MCP

Make Chutes callable from local agents.

The toolkit ships a stdio MCP server for model discovery, quota, aliases, usage, discounts, chutes, and API key read paths. Write and deploy paths keep their [BETA] labels.
Open MCP server sourceConnect editors
MCP skill sourceMCP server READMECursor setup
Read tools
Models, quota, usage, aliases, discounts, chutes, API keys
Write tools
[BETA]
Catalog checked
13 models, Jun 25, 2026
Auth
CHUTES_API_KEY=cpk_...

Full setup walkthrough

  1. 01

    Install the MCP server

    Install over stdio with uv, then run the self-check (it sends no credentials):
    install + self-check
    bash
    uv tool install chutes-mcp-server \
  --from plugins/chutes-ai/skills/chutes-mcp-portability/mcp-server

chutes-mcp-server --self-check
    Not on PyPI — use --from the local path. The chutes-mcp-server binary lands in ~/.local/bin; keep that on PATH.
  2. 02

    Generate a client config

    One generator targets every client. Pass cursor, cline, aider, hermes, or claude-desktop, then merge the snippet into that client's MCP config:
    generate_agent_config.py
    bash
    python plugins/chutes-ai/skills/chutes-mcp-portability/scripts/generate_agent_config.py cursor
python plugins/chutes-ai/skills/chutes-mcp-portability/scripts/generate_agent_config.py cline
python plugins/chutes-ai/skills/chutes-mcp-portability/scripts/generate_agent_config.py aider
python plugins/chutes-ai/skills/chutes-mcp-portability/scripts/generate_agent_config.py hermes
  3. 03

    Provide the API key

    Export CHUTES_API_KEY=cpk_... in the environment the client launches from. The server forwards it as Bearer auth.
    bash
    export CHUTES_API_KEY=cpk_...
  4. 04

    Verify over stdio

    Ask the client to list one Chutes model — it calls chutes_list_models and returns a live id.
    Read tools (models, quota, usage, aliases, discounts, chutes, API keys) are verified. Write and deploy tools keep their [BETA] labels.

What the generator writes

Each target writes a small config that points the client at the stdio server and reads the key from the environment — so secrets stay out of checked-in files.

Open generator script
Generated MCP config
json
// .cursor/mcp.json — same shape for Claude Desktop and Cline
{
  "mcpServers": {
    "chutes": {
      "command": "chutes-mcp-server",
      "env": { "CHUTES_API_KEY": "${env:CHUTES_API_KEY}" }
    }
  }
}

Tool boundary

Read tools
Model discovery, quota, aliases, usage, discounts, chutes, API key reads.
Status
Verified read paths from the toolkit.
Write tools
Alias changes, key creation, deployment, or platform operations.
Status
[BETA] labels must remain visible.

Troubleshooting

Symptom
Client cannot start the server
Likely cause
The uv-installed command is not on PATH for the client process.
Fix
Use the absolute command path from uv or launch the client from the same shell.
Symptom
Read tools work, write tool warning appears
Likely cause
The toolkit marks write tools [BETA].
Fix
Keep the label and confirm the exact action before using mutating tools.
Symptom
Inference auth fails
Likely cause
CHUTES_API_KEY is missing or sent through the wrong header.
Fix
Store cpk_... and use Authorization: Bearer.