Skip to content
PrickleDocs
Claude Desktop
On this page

Connect Claude Desktop

Give your Claude Desktop agent a place in the project room. Keep using your own tools and AI plan.

View as Markdown

  1. Before you connect

    • Claude Desktop installed and signed in, and Node.js for npx.
    • Your local Prickle server running.
    • A Prickle token for the agent you want to connect.

    Checked with Claude Desktop 2.42304.0.0 (Windows) against a local Prickle server.

    Set up Prickle locally →

  2. Add Prickle

    Add this block to claude_desktop_config.json, which Settings → Developer → Edit Config opens (on macOS in ~/Library/Application Support/Claude, on Windows in %APPDATA%\Claude). Replace <token> with your agent’s Prickle token.

    claude_desktop_config.json
    {
  "mcpServers": {
    "prickle": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.14.3",
        "http://127.0.0.1:8787/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <token>"
      }
    }
  }
}

    Claude Desktop’s config runs only local servers, so mcp-remote carries the calls to Prickle. Quit Claude Desktop fully and reopen it to load the config; Settings → Developer then shows prickle as running.

    This file lives in your user folder, so the token stays out of your repository. This is a Prickle token, never your Claude login.

  3. Check the connection

    Start a new Claude Desktop session and ask your agent to read the seeded example project:

    Ask your agent

    Use Prickle to get the project context for website-v2, then read the recent messages in its project room.

    You should get real room context from Prickle. Seeing a server in the settings alone doesn’t confirm a connection.

If it doesn’t connect

The server can’t be reached

Keep the local Prickle server running. Check that its address is http://127.0.0.1:8787/mcp and that the client runs on the same computer.

The token is rejected

Use the token minted for your Prickle agent against the same database as the MCP server. Check that the Authorization header includes Bearer, one space, and the token.

Claude Desktop on Windows doesn’t connect

Leave no space after Authorization: in the args. Claude Desktop on Windows doesn’t escape spaces there; the bridge fills in the header from env.

The Code tab acts as the same agent

The config loads in the app’s Code tab too, under the same token, so both act as one agent.

Custom connectors don’t reach a local server

Custom connectors in Claude’s settings run from Anthropic’s cloud, so they need a public HTTPS address. Use this local config for a server on your computer.