Connect Claude

The server is at https://mcp.reechee.io/mcp (Streamable HTTP). Two ways to connect: log in with your Reechee account (OAuth Connect, nothing to paste), or send an Authorization: Bearer rch_live_… header (API key). Both need a Reechee account: start free, no card needed.

Connect with your Reechee account (OAuth)

New to Reechee? Create your account and finish setup first, then add the connector. If you sign up in the middle of Connect, Claude is left waiting and you will need to click Connect again.

The easiest way in Claude Desktop and claude.ai - nothing to paste. Add a custom connector and Claude runs the login flow for you:

Settings → Connectors → Add custom connector.
Paste the URL:
https://mcp.reechee.io/mcp
Claude opens a browser to Reechee. Log in (if you aren’t already) and approve the “Connect to Reechee” screen.

That’s it - Claude holds the connection and the tools appear: the full read + action set and the credit tools (sixteen tools). The consent screen has an optional credit budget: leave it empty for no limit, or set one to cap spending. This holds on every plan, starting with pay-as-you-go. Disconnect any time from the same Connectors settings; it revokes the connection immediately.

Already set up with https://mcp.reechee.io/mcp/auth? Keep it. The /mcp/auth URL and the bare /mcp URL behave exactly the same: both ask Claude to log you in.

Credit-spending tools (unlock contact, unlock committee, generate report) spend your credits. An API key needs a spend cap. An OAuth connection can spend with no limit, or within the optional credit budget you set on the consent screen - see the authentication guide.

Claude Code

Add it with one command:

claude mcp add --transport http reechee https://mcp.reechee.io/mcp

Claude Code sees that the server needs a login and lists it as needing authentication. Run /mcp, pick reechee, and log in from the browser it opens. Or pass an API key as a header instead:

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}" }
    }
  }
}

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

Log in (recommended) - use OAuth Connect above: Settings → Connectors → Add custom connector, paste https://mcp.reechee.io/mcp, and approve. No config file. With a static API key - the custom-connector UI does the browser OAuth flow, not a static bearer header, so to pin a specific key route it 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. Then try “list my newest opportunities” - see the full toolset.

Get started

MCP

Guides

Connect with your Reechee account (OAuth)

Claude Code

Claude Desktop

Try it

​Connect with your Reechee account (OAuth)

​Claude Code

​Claude Desktop

​Try it

Connect with your Reechee account (OAuth)

Claude Code

Claude Desktop

Try it