CMP

AI assistants (MCP)

You can connect AI assistants such as Claude, Cursor or VS Code to the portal, and then manage your servers by asking in plain words:

This works through the portal's MCP server. MCP (Model Context Protocol) is the standard way AI assistants use outside tools. Open it under Account › AI assistants.

What the assistant can do

The assistant gets one tool for each call of the API. That covers instances (with power, resize, reinstall, rescue and backups), projects, SSH keys, wallet and plans, migrations, connectors, notification channels, support tickets and licences.

It always acts as you, with your role in each organization. Anything your role can't do, the assistant can't do either. If you don't name an organization, it works in the one you have open in the portal.

With a read-only token, the assistant only gets the tools that look at things. It can't change anything.

Connect an assistant

  1. Under API tokens, create a token just for the assistant, such as "Claude on my laptop". Choose Read only unless it should make changes.

  2. Open Account › AI assistants and pick your assistant: Claude Code, Claude Desktop, Cursor, VS Code or Other.

  3. Select Copy and paste the settings where the page says:

    Assistant Where the settings go
    Claude Code Run the claude mcp add command in a terminal.
    Claude Desktop Settings › Developer › Edit config, in claude_desktop_config.json. Restart Claude afterwards. This needs Node.js installed.
    Cursor ~/.cursor/mcp.json, or .cursor/mcp.json in a project.
    VS Code .vscode/mcp.json. VS Code asks for the token the first time and stores it safely.
    Other Any MCP client that supports the Streamable HTTP transport and custom headers. Use the server address and an Authorization: Bearer … header.
  4. Replace YOUR_API_TOKEN with your token (not needed for VS Code).

The server address is your portal's address followed by /mcp, such as https://portal.example.com/mcp.

Claude on the web (claude.ai) can't connect yet. Its connectors need an OAuth sign-in, which the portal doesn't offer yet.

Stay safe

If something goes wrong

What you see What to do
The assistant says it isn't authorised (401) The token is wrong, expired or revoked. Create a new one.
A tool answers HTTP 403 Your role, a read-only token, or your organization's plan doesn't allow it. The message says which.
A tool answers HTTP 422 Some fields were missing or wrong. The assistant usually fixes this itself and tries again.
No tools that make changes The token is read-only.