Install · Claude Desktop

Add ChiefLab to Claude Desktop in 60 seconds

Claude Desktop is one of many runtimes that can call ChiefLab — see install · any agent for Telegram bots, voice agents, Python, custom SDKs, etc. Claude Desktop has first-class MCP support, so the install is clean. Your Claude conversation gets drafting briefs back — Claude renders the final copy in chat.

Want to try it first? Run ChiefMO in your browser — no install, no API key.

Step 1 — Get an API key

Go to chieflab.io/get-key. 60 seconds. No email signup.

Step 2 — Edit Claude Desktop config

Open the config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

Create the file if it doesn't exist. Paste this in (or merge with existing config):

{
  "mcpServers": {
    "chieflab": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://chieflab.io/api/mcp", "--header", "Authorization: Bearer clp_dev_<paste-your-key>"]
    }
  }
}

Uses mcp-remote as a stdio bridge to the hosted HTTPS endpoint. Replace clp_dev_<paste-your-key> with your real key from /get-key.

Step 3 — Restart Claude Desktop

Quit Claude Desktop fully (Cmd+Q on Mac, close all windows on Windows) and reopen. The MCP server icon should appear in the input area.

Step 4 — Use it

In a Claude conversation:

I just built an AI product at https://your-product.example.com.
Help me launch it. Use ChiefMO.

Claude will pick chiefmo_diagnose_marketing and call ChiefLab. Returns:

  • Positioning diagnosis
  • Drafted launch assets (posts, copy, optionally images)
  • Proposed actions — approval-gated
  • A signed reviewUrl at chieflab.io/runs/<id>?token=...

Click the reviewUrl. No login. Renders the assets visually. Approve or reject.

Multi-tenant: serving your own customers

If you're building an AI product that serves end-users, register each end-user as a tenant first. See the Cursor install page for the full multi-tenant flow — same MCP tools, different client.

Troubleshooting

  • Tools don't appear: fully quit Claude Desktop and reopen. MCP loads only on launch.
  • Tools fail with 401: Bearer token missing or wrong. Get a new key at /get-key.
  • Hosted MCP doesn't work in Claude Desktop: as of now, Claude Desktop's hosted MCP support is via stdio bridges. The local stdio config above is the most reliable path.

Other clients

  • Install in Cursor
  • More install pages shipping per platform — Codex, Base44, Hermes, OpenClaw