Fallback · Claude Desktop

Claude Desktop — manual setup

Most users never see this page. The default path is one command: say launch this in your Claude chat and let your agent run launch-here for you. This page exists only as a fallback when auto-attach can't run.

Default path: /install · Manual config below.

1. Get a key

chieflab.io/get-key → copy the clp_dev_ or clp_live_ key.

2. Edit Claude Desktop config

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

Create if missing. Paste (or merge):

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

Uses mcp-remote as a stdio bridge to the hosted HTTPS endpoint. Claude Desktop today reads MCP via stdio, so the bridge is the most reliable path.

3. Restart Claude Desktop

Fully quit (Cmd+Q on Mac, close all windows on Windows) and reopen. The MCP server icon appears in the input area. Ask: launch this. Claude picks chieflab_launch_product, drafts render inline, you approve in chat.

Troubleshooting

  • Tools don't appear: fully quit Claude Desktop and reopen. MCP loads only on launch.
  • 401 Unauthorized: Bearer token wrong. Re-mint at /get-key.
  • Hosted MCP "url" field unsupported: stick with the stdio bridge config above — Claude Desktop's remote-MCP support is still rolling out.

More