MCP server

Kadmo hosts an MCP server at https://app.kadmo.ai/mcp. Connect Claude, Claude Code, Cursor, VS Code, Codex or your own script to it, and that client can drive your Kadmo account: dispatch work to your agents, read tasks and runs back, and edit your skill pack, playbooks, roles, workflows and routing. There is nothing to install — the server runs in Kadmo, and every client signs in as you.

What it is for

You want to…	Tools to look at
See your agents and send one a job	list_agents, get_agent_status, dispatch_agent_job, queue_jobs, run_workflow
Work a ticket end to end with a playbook	list_playbooks, work_on_task
Find out what happened on a ticket	get_task, review_tasks, get_run_transcript
Fix or extend what agents know	get_pack, read_pack_file, write_pack_file, scaffold_pack_node
Change how tickets are routed and run	get_issue_type_routing, set_issue_type_routing, manage_playbook, manage_workflow, manage_role

Every tool acts as the signed-in member, on that member's account only. The full list with parameters is on MCP tools.

Connect a client

The app shows these setups with copy buttons under Settings → Assistant → Connect an MCP client. Every client uses the same URL over Streamable HTTP, and every setup registers the server under the name kadmo.

Client	Sign-in
Claude.ai and Claude Desktop	OAuth
Claude Code	OAuth
Cursor	OAuth
VS Code	OAuth
Codex	OAuth
Headless (.mcp.json) — CI, a script, an agent	Personal token

Claude.ai and Claude Desktop

1. Open Settings → Connectors and choose Add custom connector.
2. Name it kadmo and paste the URL:

https://app.kadmo.ai/mcp

3. Choose Connect and sign in. The connector gets its own token, listed under Connected clients in Kadmo.

Claude Code

claude mcp add --transport http kadmo https://app.kadmo.ai/mcp

Then run /mcp in Claude Code and choose Authenticate to sign in.

Cursor

In ~/.cursor/mcp.json:

{
  "mcpServers": {
    "kadmo": {
      "url": "https://app.kadmo.ai/mcp"
    }
  }
}

Enable it in Cursor Settings → MCP and sign in when Cursor asks.

VS Code

In .vscode/mcp.json:

{
  "servers": {
    "kadmo": {
      "type": "http",
      "url": "https://app.kadmo.ai/mcp"
    }
  }
}

Start it from the file or the MCP view and sign in when VS Code asks.

Codex

In ~/.codex/config.toml:

[mcp_servers.kadmo]
url = "https://app.kadmo.ai/mcp"

Then sign in:

codex mcp login kadmo

A headless client with a personal token

For a client that cannot open a browser, create a personal token (below) and put it in .mcp.json:

{
  "mcpServers": {
    "kadmo": {
      "type": "http",
      "url": "https://app.kadmo.ai/mcp",
      "headers": { "Authorization": "Bearer kadmo_pat_your-token" }
    }
  }
}

Keep the file out of version control, or read the token from an environment variable your client supports.

OAuth or a personal token

	OAuth	Personal token
For	Every client that can open a browser	CI, scripts, agents — anything headless
How you get it	The client opens Kadmo's sign-in the first time it connects	Settings → Assistant → Personal tokens → Create token
Looks like	Managed by the client	kadmo_pat_ followed by a secret
Lifetime	Access for one hour, renewed automatically by the client for up to 30 days of inactivity	Until you revoke it
Listed under	Connected clients, with when it connected and was last used	Personal tokens, with its name, first characters, creation and last use
Ends when	You revoke it, sign in again from the same client (which replaces it), or you are removed from the account	You revoke it, or you are removed from the account

OAuth grants one scope, mcp. Either way the client can do everything your role allows on your account — there is no narrower token.

Create a personal token

1. Go to Settings → Assistant and scroll to Personal tokens on the Connect an MCP client card.
2. Enter a Token name — the client it is for, up to 80 characters — and press Create token.
3. Copy the token now. It is shown once and never again.

A member can hold up to 50 live tokens. Tokens are personal: every member sees and revokes only their own, and a personal token is used only for the MCP server.

Revoke access

Press Revoke next to a token or a connected client. Its next call is refused; signing in again from the client reconnects it.

Turning the server off for the account

The MCP server can be switched off for the whole account. Under Settings → Assistant → MCP Connections, the Kadmo Cloud toggle controls the tools available to MCP clients, the chat assistant and the Slack bot. Only an Admin can change it.

While it is off, clients still connect and sign in, but they list no tools, and every tool call answers with the reason. The Connect card shows a warning while the switch is off.

What your role allows

Most tools are open to every member. Seven tools change the account's content and need the Admin role: write_pack_file, scaffold_pack_node, delete_pack_node, manage_playbook, manage_role, manage_workflow, set_issue_type_routing. The Connect card lists them and says whether you have the role.

A trial that has ended blocks those seven, sync_pack, and the four tools that dispatch work (dispatch_agent_job, queue_jobs, run_workflow, queue_workflow). Dispatching is also subject to your account's daily usage cap.

Errors and fixes

A tool that refuses returns a tool result whose text starts with a machine code, so the model can act on it. Connection problems come back as HTTP errors.

What you see	Cause	Fix
The client asks you to sign in again, or reports 401	The token expired, was revoked, or you were removed from the account	Sign in again from the client, or create a new personal token
404 on connect	The client is configured on an old URL such as /mcp/sse	Remove the server and add it again with https://app.kadmo.ai/mcp
405	Something sent a GET (for example a browser)	Nothing to fix — the endpoint accepts POST only; connect with an MCP client
406	A hand-written request did not accept both application/json and text/event-stream	Send Accept: application/json, text/event-stream
403 forbidden_origin	A web page on another site called the server	Use an MCP client; only Claude's web connectors and Kadmo itself may call from a browser
Connected, but no tools listed	The Kadmo Cloud switch is off for the account	Ask an Admin to turn it on under Settings → Assistant → MCP Connections
admin_required (403)	The tool needs the Admin role	Ask an Admin, or have your role raised on the Team page
trial_expired (402)	The account's trial has ended	Upgrade the account (see Account)
daily_cap_reached	The account reached its daily usage cap	Try again the next day
stale_base_sha (409)	A pack file changed since the client read it	Read the file again and re-apply the change — the refusal carries the latest content
invalid_pack_file (422)	A pack file or workflow failed validation	Fix the fields the error lists; nothing was committed
pack_not_writable (403)	Kadmo is not allowed to write to your own pack repository	Turn on pack editing for the account (see Skill packs)
You already have 50 tokens — revoke one you no longer use first	The personal-token limit	Revoke a token you no longer use

The runtime's local MCP server

The Kadmo runtime on your own computer is a separate, local MCP server: kadmo mcp serves your installed skill packs, your workflows and your Chrome over stdio. See The MCP server: kadmo mcp.