Multicloud MCP Server
Connect AI assistants to the Multicloud platform via the Model Context Protocol
Getting Started
Create an Account
If you don't have an account yet, sign up here.
Generate an API Key
Go to Account > API keys, click "Create key", name the key and pick its scopes (see the table below). Copy the key value. It starts with mca_ and the page shows it only once. Only organization owners can create keys.
Configure Your AI Assistant
Choose your AI assistant below and follow the integration instructions.
Key scopes and tools
Every key has the same format (mca_) and carries one or more scopes. The scopes decide which tools the key can call. Pick the scopes for your use case when you create the key.
| Use case | Scope | Tools |
|---|---|---|
| Look up prices, availability and locations | catalog | get_server_details, compare_servers, get_locations, get_providers, advanced_server_search, get_valid_field_values |
| Read account, billing and CI pool data | org:read | get_account_overview, get_billing, list_org_pools, get_pool_cluster, list_pool_classes |
| Change a CI pool (includes org:read) | org:write | update_ci_pool |
| Delete, hibernate and wake pools (includes org:read only, not org:write) | org:admin | the org:read tools |
| Manage Extend pools and peerings (paid; shown only when Extend is enabled for your account) | extend | list_pools, get_pool, hibernate_pool, wake_pool, create_extend_pool, delete_pool, create_peering, list_peerings, delete_peering |
| Connect and verify your cloud accounts (paid; includes org:read) | infra | No MCP tools. Send the key as the X-API-Key header to /api/v1/orgs/{slug}/cloud-accounts |
One key can hold several scopes. An account can have up to 25 keys, and up to 10 of them can carry the Extend scope.
Auditing your own cluster
Everything on this page connects your assistant to the Multicloud catalog. The Multicloud Advisor is a second, separate MCP server: it runs inside your Kubernetes cluster, reads it read-only, and answers one question — what would the same work cost somewhere else?
It is never exposed to the internet. Your assistant reaches it through your own kubectl port-forward, so your Kubernetes RBAC is the gate. It does need a catalog key, which your agent writes straight into a Kubernetes Secret.
Claude Code
claude plugin marketplace add multicloud/skills && claude plugin install multicloud-advisor@multicloudThen ask it to audit your cluster. It handles the install, the tunnel and the registration.
Any other agent
Point it at the skill and tell it to follow the instructions there. Same content, fetched fresh each session — you just have to ask for it by name.
https://multicloud.io/agent/skill.mdReviewing this before approving it? What the agent does covers scope, permissions, blast radius and revocation — no login required.
Integration Instructions
Click on your AI assistant to view setup instructions:
Send the key as Authorization: Bearer mca_.... A static Authorization header turns off the OAuth flow in your client.
The X-API-Key header is deprecated. Never send both headers: the server answers 400. Legacy UUID keys stopped working on 2026-10-24. Create a new mca_ key instead.
Alternative: OAuth2 Authentication
In addition to API key authentication, our MCP server also supports OAuth2 authentication. This provides a more secure and user-friendly authentication flow. OAuth sign-in gives you the catalog tools only. Pool and account tools need an mca_ key with the matching scope.
OAuth2 Setup Requirements
- Create a Multicloud account (if you haven't already)
- Use the client ID: multicloud-mcp-client
- Configure OAuth scopes: openid
MCPJam Configuration
For MCPJam users, you can configure OAuth2 authentication as shown in the screenshot above:
- Set Authentication to "OAuth 2.0"
- Check "Use custom OAuth credentials"
- Enter multicloud-mcp-client as the Client ID
- Set OAuth Scopes to openid
- Use the URL: https://mcp.multicloud.io/mcp
Note: OAuth2 authentication provides automatic token refresh and better security compared to static API keys. Choose this method if your MCP client supports OAuth2 flows.
Need Help?
If you encounter any issues during setup, please check:
- Your API key is correctly copied (no extra spaces)
- "Needs authentication", or an mcp-remote RegistrationRejectedError or 403 on client registration: the key is missing, revoked or a legacy UUID key. Create a new mca_ key.
- A scope error: add the scope the tool needs to the key (see the table above). Create a new key if needed.
- 503: the server could not check the key. Retry in a few seconds.
- Your AI assistant is up to date
- The configuration file syntax is valid JSON
- You have an active internet connection