Claude Desktop

1. Mint a key

In the dashboard at thebreeth.com/app/api-keys, create a key with write scope (add admin if you want the agent to retract). Copy the ck_live_… value.

2. Open the Claude Desktop config

OS	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`

If the file doesn't exist, create it.

3. Add the Breeth server

Add (or merge into) mcpServers:

{
  "mcpServers": {
    "breeth": {
      "transport": "http",
      "url": "https://mcp.thebreeth.com/mcp",
      "headers": {
        "Authorization": "Bearer ck_live_..."
      }
    }
  }
}

Replace ck_live_... with the key you copied.

4. Restart Claude Desktop

Fully quit the app (not just close the window) and reopen. The Breeth tools should now appear in the tool list — add_episode, record_fact, search, retract.

5. Try it

In a Claude conversation, ask: "Remember that I prefer Rust over Go for IO-heavy services." Claude will call add_episode and confirm the write.

Then in a fresh conversation: "What do I prefer for IO-heavy services?" Claude calls search and pulls your prior fact back.

Multi-team keys

If your key is bound to more than one team, add "X-Cogram-Team-Id": "<team_uuid>" alongside the Authorization header. Otherwise the server picks the first team on the key.

Troubleshooting

Tools don't appear. Verify the config JSON is valid (no trailing commas). Check Claude Desktop's MCP logs from the Developer menu.

Calls 401. Key is wrong, revoked, or expired. Mint a new one.

Calls 429. You've hit your monthly cap. Check Tiers & Limits and either wait for the period reset or upgrade.

Calls 402. Subscription is past-due. Resolve in the dashboard's billing portal.

What gets stored

Every memory Claude writes through MCP lands in your team's active project. It's visible to every member of the team in the dashboard graph. See Projects & Teams for the isolation model.