Connect Cursor

The server is at https://mcp.reechee.io/mcp (Streamable HTTP). Add it to Cursor’s MCP config - global at ~/.cursor/mcp.json, or per-project at .cursor/mcp.json.

Log in with OAuth

Cursor (v1.0+) supports the browser login flow. Point it at the /mcp/auth URL:

{
  "mcpServers": {
    "reechee": {
      "url": "https://mcp.reechee.io/mcp/auth"
    }
  }
}

Open Settings → MCP and Cursor shows a Login / Needs authentication button for the reechee server - click it, log in, and approve the “Connect to Reechee” screen. No key to paste; the tools follow your team’s current plan (a paid team gets twelve tools, fifteen with a consent-time credit budget - see the authentication guide). If your Cursor is older or you prefer a key, use one of the options below instead.

Anonymous

{
  "mcpServers": {
    "reechee": {
      "url": "https://mcp.reechee.io/mcp"
    }
  }
}

With an API key

Add a headers block. Use an env var so the key stays out of the file:

{
  "mcpServers": {
    "reechee": {
      "url": "https://mcp.reechee.io/mcp",
      "headers": { "Authorization": "Bearer ${env:REECHEE_API_KEY}" }
    }
  }
}

(You can also paste the literal Bearer rch_live_… value instead of the env var.)

Try it

Save the file, then open Settings → MCP and make sure reechee shows a green dot (toggle it on or refresh if needed). In a chat, ask:

What are people unhappy about with Zendesk lately?

Once connected (OAuth or key) you also get opportunities, watchlist, and triage - see the full toolset.

Cursor auto-detects the transport from the URL. If the server doesn’t connect, refresh the MCP settings or restart Cursor so it re-reads the config.

Get started

MCP

Guides

Log in with OAuth

Anonymous

With an API key

Try it

​Log in with OAuth

​Anonymous

​With an API key

​Try it

Log in with OAuth

Anonymous

With an API key

Try it