Skip to main content
The server is at https://mcp.reechee.io/mcp (Streamable HTTP). Anonymous gets the 3 free tools; add an Authorization: Bearer rch_live_… header for the full set.

​
Claude Code

Add it with one command: 
claude mcp add --transport http reechee https://mcp.reechee.io/mcp
With an API key, pass the header: 
claude mcp add --transport http reechee https://mcp.reechee.io/mcp \
  --header "Authorization: Bearer rch_live_YOUR_KEY"
Or commit it to a project’s .mcp.json (env-var expansion works, so the key stays out of the file): 
{
  "mcpServers": {
    "reechee": {
      "type": "http",
      "url": "https://mcp.reechee.io/mcp",
      "headers": { "Authorization": "Bearer ${REECHEE_API_KEY}" }
    }
  }
}
For anonymous access, drop the headers block. Check the connection with /mcp.
If a key is set but rejected, Claude Code reports the server as failed (it does not fall back to a login prompt). Double-check the key if the connection won’t come up.

​
Claude Desktop

Anonymous - use the built-in connector UI: Settings → Connectors → Add custom connector, paste https://mcp.reechee.io/mcp, and add it. With an API key - the custom-connector UI handles OAuth, not a static bearer header, so route a keyed connection through the mcp-remote bridge (needs Node/npx). Edit claude_desktop_config.json:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "reechee": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://mcp.reechee.io/mcp",
        "--header", "Authorization: Bearer rch_live_YOUR_KEY"
      ]
    }
  }
}
Restart Claude Desktop after saving. (mcp-remote is a community bridge, not an Anthropic package.)

​
Try it

Ask:
What are people unhappy about with Zendesk lately?
Claude resolves the product and reads its pain points. With a key, try “list my newest opportunities” - see all 11 tools.