Camber MCP

CamberCloud runs a remote Model Context Protocol (MCP) server. Register it in your editor or CLI with your Camber API token, then use tools such as agents_chat to talk to Camber agents with the same @mention tags as in Nova.

The page has four parts: Set up Camber MCP (shared for every client), MCP clients (Claude Code CLI, Claude Code VS Code extension, Cursor, and Claude Desktop), Context Mirror (sync local project context into Camber), and Camber MCP tools (technical reference).

Set up Camber MCP

Get your Camber API key

The value you pass as <YOUR_CAMBER_API_KEY> is your Camber API token:

1. Log in to app.cambercloud.com
2. Open your profile settings
3. Copy your API token

For using that token with the Camber CLI (environment variable, one-off flags), see Login — API token.

Camber MCP server endpoint

Every client must use this HTTP MCP endpoint:

https://camber-mcp.cambercloud.com/mcp

Pair it with an Authorization header: Bearer <YOUR_CAMBER_API_KEY> (see above).

Shared MCP JSON (reference)

Most clients accept a server entry named camber-mcp with the same fields. This is the shape Claude Code uses in a project .mcp.json; Cursor often uses in a project .cursor/mcp.json.

{
  "mcpServers": {
    "camber-mcp": {
      "type": "http",
      "url": "https://camber-mcp.cambercloud.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_CAMBER_API_KEY>"
      }
    }
  }
}

Replace <YOUR_CAMBER_API_KEY> with your token from Get your Camber API key.

MCP clients

Claude Code, Cursor, and Claude Desktop all connect to the same Camber MCP server. Complete Set up Camber MCP first, then follow the subsection for your client. Agent addressing uses the same @mention tag formats as in Nova.

Claude Code

Claude Code is Anthropic’s agentic CLI (and related editor flows). Install and sign in per Anthropic’s documentation, then register the Camber server.

Global (all projects on this machine):

claude mcp add --transport http camber-mcp \
  https://camber-mcp.cambercloud.com/mcp \
  --header "Authorization: Bearer <YOUR_CAMBER_API_KEY>"

Project-only (current repository):

claude mcp add --transport http camber-mcp \
  https://camber-mcp.cambercloud.com/mcp \
  --header "Authorization: Bearer <YOUR_CAMBER_API_KEY>" \
  --scope project

Alternatively, add a project .mcp.json using the shared MCP JSON shape.

Use agents in Claude Code

In the Claude Code terminal, you can invoke Camber agents with the camber CLI pattern (your UI may show the agents_chat tool and JSON). Example:

camber @username.agent_alias Your question here

Example: camber @camberuser.titanic How many passengers?

Claude Code for VS Code

If you use Claude Code through the VS Code extension, follow these steps:

1. Create a .mcp.json file in your project root with the shared MCP JSON shape:

{
  "mcpServers": {
    "camber-mcp": {
      "type": "http",
      "url": "https://camber-mcp.cambercloud.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_CAMBER_API_KEY>"
      }
    }
  }
}

2. Open a new Claude Code session or restart VS Code.
3. In the Claude chat panel, type /mcp and select MCP servers.
4. Click on camber-mcp and click Enable.

Use agents in the VS Code extension

Once connected, start a chat in the Claude Code panel. Address Camber agents the same way as in the terminal:

camber @username.agent_alias Your question here

Cursor

Cursor connects to MCP servers from Settings and/or JSON config files. Cursor’s MCP UI and file locations change between releases—use Cursor’s MCP documentation for the exact panel names on your version.

1. Open Cursor Settings.
2. Go to the Tools & MCPs section.
3. Select Add a Custom MCP Server button.

Use agents in Cursor

1. Open Chat or Composer (or Agent mode, if available).
2. Start a thread where MCP tools are allowed—Cursor should list tools from camber-mcp (for example agents_chat, agents_list).
3. Address your agent with the same tags as in Nova: @<username>.<agent_alias> or @<teamname>.<agent_alias>.

If tools do not appear, confirm the server is enabled in MCP settings, your token is valid, and your Cursor build supports HTTP MCP for remote URLs.

Claude Desktop

Claude Desktop connects to MCP servers through its config file. Because Claude Desktop supports stdio servers, use mcp-remote (via npx) to bridge to the remote Camber HTTP endpoint.

1. Open Claude Desktop.
2. Open Settings (from the menu bar, or the ☰ menu inside the app).
3. Go to the Developer tab.
4. Click Edit Config. Claude Desktop opens (or creates) the claude_desktop_config.json file and reveals it in your file explorer.
5. Open claude_desktop_config.json in a text editor and add the camber-mcp server entry below (merge it into any existing mcpServers object):

{
  "mcpServers": {
    "camber-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://camber-mcp.cambercloud.com/mcp",
        "--header",
        "Authorization: Bearer <YOUR_CAMBER_API_KEY>"
      ]
    }
  }
}

6. Replace <YOUR_CAMBER_API_KEY> with your token from Get your Camber API key, then save the file.
7. Restart Claude Desktop (quit completely and reopen) so it picks up the new server.

Use agents in Claude Desktop

Once Claude Desktop restarts, you can call camber-mcp tools (for example agents_chat, agents_list) from chat box. Address your agent with the same tags as in Nova: @<username>.<agent_alias> or @<teamname>.<agent_alias>.

Camber MCP tools

The camber-mcp server currently exposes these tools:

Your MCP client also shows the live parameter schema for each tool.

user_info

Shows the Camber account connected to MCP, including your username, email, and teams. This is useful when you want to confirm which personal or team workspace your agents belong to.

Example response:

{
  "email": "user@example.com",
  "username": "camberuser",
  "teams": [
    {
      "display_name": "Research Team",
      "team_name": "research-team"
    }
  ]
}

agents_create

Create a Camber agent. Creates a personal agent by default; pass team_name to create the agent for a team you belong to.

agents_chat

Chat with a Camber agent by tag and message. Returns the agent’s reply as text.

Use agents_chat from Claude Code (for example via the camber CLI pattern shown above) and from Cursor when camber-mcp tools are available in Chat, Composer, or Agent mode.

agents_list

List Camber agents you can use, with optional scope and pagination. Returns agent metadata and page info (for example total count and page size).