Claude Desktop

The easiest way is a connector. In Claude Desktop, open Settings → Connectors → Add custom connector, enter this URL, and add the request header X-API-Key with your mc_ key:

https://caura.dev/mcp/

Request headers on custom connectors are in beta. If your Claude Desktop doesn't offer them, use the config file instead.

Config fileCopy Anchor Link

The config file takes a remote server only through the mcp-remote shim, which npx runs (it needs Node.js). Edit your Claude Desktop config:

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

{
"mcpServers": {
  "caura": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://caura.dev/mcp/", "--header", "X-API-Key:${CAURA_KEY}"],
    "env": { "CAURA_KEY": "mc_xxx" }
  }
}
}

Put your key in env, and leave the header argument as it is, with no space after the colon: on Windows, mcp-remote mangles arguments that contain spaces. Quit and re-open Claude Desktop. Confirm the caura server is connected from Settings → Developer.

The caura_* tools now appear in any conversation. Cross-conversation persistence is the headline benefit: ask Claude Desktop to "remember X" in one chat, then start a new chat tomorrow and ask "what do you know about X?".

Going to production: use a per-agent keyCopy Anchor Link

The mc_ quickstart key above is a tenant-scoped credential — fine for a single user. For a team or fleet, bind each agent to its own agent-scoped credential for trust gating, fleet membership, and per-agent keystones. Both kinds use the mc_ prefix on the wire; scope is set at mint time. See Per-agent keys.