Claude Desktop

A remote connector in settings, or the stdio bridge on plans without them.

Setup

1. Open Settings and look for Connectors (sometimes under Integrations).
2. Add a custom connector with the URL below and your key as an x-api-key header.
3. Restart Claude Desktop.
4. Start a chat and check the tools appear in the tool menu.

https://api.unzoi.com/mcp
x-api-key: nai_your_key_here

If your plan has no custom-connector option, bridge through stdio

          {
  "mcpServers": {
    "unzoi": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.unzoi.com/mcp",
        "--header", "x-api-key:${UNZOI_KEY}"
      ],
      "env": { "UNZOI_KEY": "nai_your_key_here" }
    }
  }
}
        

What differs here

• Remote connectors are not available on every plan. The stdio bridge above works on all of them and is the usual fallback — see the mcp-remote page for what it is doing.
• The config file lives under your user Library (macOS) or AppData (Windows); the app shows the exact path from Settings → Developer → Edit Config, which is more reliable than any path written down here.
• Because a desktop config file is a plain JSON file in your home directory, it is a credential store. Treat it like one.

Next

• Get a key at console.unzoi.com, if you have not.
• The tool reference — what the model is reading when it chooses between the six tools.
• Stories for context windows — the one habit that most changes how well an agent works against this API.
• Limits — an agent that loops can spend a monthly quota faster than you expect.
• Claude Desktop's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.

Endpoint, for copying: https://api.unzoi.com/mcp