Cursor MCP [BETA]

Bring Chutes tools into Cursor with MCP.

Cursor discovers Chutes through a workspace .cursor/mcp.json generated by the toolkit. Read tools are active; write paths keep [BETA] labels.
Open source guideConnect quickstarts
Cursor setupMCP server READMEMCP tool map
Status
MCP read tools active; write tools [BETA]
Base URL
https://llm.chutes.ai/v1
Live model example
Qwen/Qwen3-32B-TEE
Catalog checked
Jun 25, 2026; context 40K

Full setup walkthrough

Everything you need is on this page — no need to leave for the toolkit. Each step is copy-paste runnable and uses a live model id from the catalog.

  1. 01

    Install the Chutes MCP server

    uv tool install
    bash
    uv tool install chutes-mcp-server \
  --from plugins/chutes-ai/skills/chutes-mcp-portability/mcp-server
    The package is not on PyPI — the --from <local path> form is required. The chutes-mcp-server binary lands in ~/.local/bin; make sure that is on your PATH.
  2. 02

    Generate the workspace config

    Run the generator with --target cursor. It writes .cursor/mcp.json in your workspace:
    generate + .cursor/mcp.json
    json
    python plugins/chutes-ai/skills/chutes-mcp-portability/scripts/generate_agent_config.py \
  --target cursor --out /path/to/your/workspace

# Writes .cursor/mcp.json:
{
  "mcpServers": {
    "chutes": {
      "command": "chutes-mcp-server",
      "env": { "CHUTES_API_KEY": "${env:CHUTES_API_KEY}" }
    }
  }
}
  3. 03

    Provide the API key

    Store your cpk_ key as CHUTES_API_KEY in the environment or a secret store. Send it as Authorization: Bearer — never X-API-Key, which inference ignores.
    bash
    export CHUTES_API_KEY=cpk_...
    Cursor reads ${env:CHUTES_API_KEY} from the environment, not .env.local. Put the export in the shell profile Cursor inherits.
  4. 04

    Restart Cursor and verify

    Restart Cursor (File → Restart Window), open the MCP panel, expand the chutes server, and call chutes_list_models with limit 1.
    "Command not found: chutes-mcp-server" → add ~/.local/bin to PATH. A 401 means the key is empty or the wrong profile.

MCP tool boundary

Read tools
Model discovery, quota, aliases, usage, discounts, chutes, and API key reads.
Status
Active through the MCP server.
Write tools
Any action that mutates account or compute state.
Status
[BETA] and should require explicit user confirmation.

Troubleshooting

Symptom
The model ID fails
Likely cause
The catalog changed or the client cached model metadata.
Fix
Refresh /v1/models and update the config.
Symptom
Auth falls into anonymous limits
Likely cause
The key is missing or not sent as Bearer auth.
Fix
Export CHUTES_API_KEY=cpk_... and send Authorization: Bearer.
Symptom
Routing aliases fail
Likely cause
Saved default aliases need a dashboard Model Routing pool.
Fix
Use a concrete model ID or an inline comma-separated pool first.