Skip to main content
The server is at https://mcp.reechee.io/mcp (Streamable HTTP). Three ways to connect: log in with your Reechee account (OAuth Connect, no key), send an Authorization: Bearer rch_live_… header (API key), or use it as a guest for the 3 Guest tools, no login.

​
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 - no key to paste. Add a custom connector pointed at the /mcp/auth URL and Claude runs the login flow for you:
  1. Settings → Connectors → Add custom connector.
  2. Paste the URL:
  3. 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. What you get follows your team’s current plan: a free-plan team gets the 3 Guest tools tied to your account, a paid team gets the full read + action set (twelve tools - sixteen if you allow an optional credit budget on the consent screen). Disconnect any time from the same Connectors settings; it revokes the connection immediately.
Use the bare https://mcp.reechee.io/mcp (no /auth) only if you want Guest access - it answers without asking you to log in, so Claude won’t offer the Connect flow. The /mcp/auth URL is what triggers the browser login. On claude.ai, Guest requests come from Anthropic’s servers, so the Guest limit is shared with everyone using Guest there. Connect with your account to get a limit of your own.
Credit-spending tools (unlock contact, unlock committee, generate report, generate pitch) need a spend budget: an API key with a spend cap, or an OAuth connection where you allowed the optional credit budget on the consent screen - see the authentication guide.

​
Claude Code

Claude Code connects with a header, not the browser flow. Add it with one command:
With an API key, pass the header:
Or commit it to a project’s .mcp.json (env-var expansion works, so the key stays out of the file):
For Guest 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

Log in (recommended) - use OAuth Connect above: Settings → Connectors → Add custom connector, paste https://mcp.reechee.io/mcp/auth, and approve. No config file. Guest - same connector UI, but paste the bare https://mcp.reechee.io/mcp (no /auth) for the 3 Guest tools without logging in. 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
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. Once connected (or keyed), try “list my newest opportunities” - see the full toolset.