Camber MCP

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 (Agent tags).

The page has three parts: Set up Camber MCP (shared for every client), MCP clients: Claude Code and Cursor, and Camber MCP tools (technical reference).

Set up Camber MCP

ℹ️
Heads-up: To use the full Camber environment through Camber MCP, you need the Camber CLI on your computer. If you do not have it yet, Camber MCP setup will install the CLI for you. If you are not logged in to Camber, you will need to log in as well (your API key in the MCP client is for the remote server). See Installation for details.

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 and Cursor both 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—see Agent tags in AI Agents.

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.

⚠️
Claude Pro (or eligible plan) required: Claude Code needs an active Claude Pro subscription or another plan that includes Claude Code. CamberCloud does not replace Anthropic’s requirements.

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 terminal: Camber MCP calling the Titanic agent via agents_chat

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.
ℹ️
Tokens and Git: Do not commit real API keys. Use a placeholder in committed .cursor/mcp.json and set your token locally, or rely on a private, gitignored override file if your team uses that pattern.

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> (see Agent tags).

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.

Camber MCP tools

This section summarizes selected tools exposed by the camber-mcp server. Your MCP client lists the full tool set and parameters.

agents_chat

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

ParameterDescription
agent_tagTag of the agent to use. Include the leading @; format is @<owner_name>.<agent_alias> (for example, @camber_user.ai-agent-1).
messageThe message to send to the agent.
model_idModel name for the agent run (for example, Haiku, Sonnet). Default is claude-sonnet-4-6.

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).

ParameterDescription
scopeWhich agents to include: community (community agents), system (system agents), or team (agents for a specific team). Omit or leave unset to list your personal agents.
team_nameWhen scope is team, the team’s unique name. Ignored for other scopes.
pagePage number to fetch (default: 1).
sizeAgents per page (default: 20).