Sign in (recommended — no token)

Most MCP clients now let you sign in directly. Add the endpoint above and your tool opens a browser asking you to sign in to ReachRobin and approve access — there’s nothing to copy or paste, and no token to rotate. Access is tied to your ReachRobin account and the credential refreshes automatically.

claude.ai & the Claude desktop app

Open Settings → Connectors → Add custom connector, paste https://mcp.reachrobin.com/api/mcp, and click Connect. A ReachRobin sign-in window opens — approve it and the tools appear. No token, no JSON.

Claude Code (CLI)

Add the server with no auth header, then authenticate in the browser:

claude mcp add --transport http reachrobin https://mcp.reachrobin.com/api/mcp

Then run /mcp inside Claude Code and choose Authenticate— it opens your browser to sign in. (If you added it with an Authorizationheader, it stays on that token instead and won’t prompt.)

ChatGPT & other MCP clients

Add a custom connector pointing at https://mcp.reachrobin.com/api/mcp with no auth header. Any client that supports MCP sign-in (OAuth) discovers the flow automatically and prompts you to log in. If your client only accepts a static header, use a token instead (below).

Or connect with a token

Prefer a static credential — for automation, or a client that only supports an Authorization header? Create a token and paste it in.

1. Create a token

Sign in to ReachRobin and go to Settings → MCP tokens. Click New token, give it a label, and hit Create. The raw token is shown exactly once. Copy it before closing the dialog.

2. Paste the token into your AI tool

Right after creation, we show two ready-to-paste JSON snippets — pick the one that matches your tool. Tokens are prefixed rr_mcp_.

Claude Code (one-liner CLI — easiest)

If you use the Claude Code CLI, skip the JSON. Run one of these — pick the scope you want:

claude mcp add --scope user --transport http reachrobin \
  https://mcp.reachrobin.com/api/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

ChatGPT (custom connector)

In ChatGPT, open Settings → Connectors → Add custom connector. Paste https://mcp.reachrobin.com/api/mcp as the URL and Bearer YOUR_TOKEN as the authorization header. No JSON editing required.

Cursor / Windsurf / Claude Code .mcp.json

Native Streamable-HTTP clients. Drop this into ~/.cursor/mcp.json, project-level .cursor/mcp.json, or .mcp.json for Claude Code. The type: "http" field is required by Claude Code (Cursor accepts it harmlessly):

{
  "mcpServers": {
    "reachrobin": {
      "type": "http",
      "url": "https://mcp.reachrobin.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Claude Desktop

Claude Desktop’s claude_desktop_config.json is stdio-only — it does not accept a bare url field for remote servers. To reach ReachRobin from the desktop app you bridge through the mcp-remote npm package, which runs locally as a stdio MCP server and proxies to our HTTPS endpoint. You need Node.js installed:

{
  "mcpServers": {
    "reachrobin": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.reachrobin.com/api/mcp",
        "--header",
        "Authorization:Bearer YOUR_TOKEN"
      ]
    }
  }
}

Note the colon-without-space in Authorization:Bearer — spaces inside argsaren’t always escaped by Claude Desktop.

Alternatively, if you use claude.ai in the browser, add ReachRobin as a Custom Connector under Settings → Connectors — point it at https://mcp.reachrobin.com/api/mcp and paste the token when prompted; no JSON editing required.

Restart the AI tool after saving. You should see the ReachRobin tools appear in its tool list. So far we’ve verified the Cursor snippet against Cursor v1.0+ and the Claude Desktop snippet via mcp-remote; other clients (Windsurf, Zed, custom agents) generally accept one of these two shapes.

Available tools

However you connect, you have access to 60tools, grouped by domain. Every tool respects your plan limits and role — if your AI tries something you don’t have permission for, you’ll get a clear error back.

Rate Limiting

• 200 requests per minute per token (shared across all tool calls).
• Invitations are not sent directly via MCP. They flow through campaign automation.
• Applicable limitson messaging, enrichment, and invitations depend on your plan and any top-ups — not the MCP layer. The quotas that apply to you are the same ones that apply to your account in the app.

When you hit a limit the tool returns 429 with a resetAt timestamp. Your AI can wait and retry automatically.

Privacy & security

• Sign-in (OAuth) connectionsdon’t hand your tool a long-lived secret — it holds a short-lived access token, refreshed automatically, scoped to your ReachRobin account. Remove the connector in your AI tool to disconnect it. The notes below apply to token connections.
• We store only a hash of the token — the raw value is shown once at creation and is unrecoverable afterwards. Lose it? Revoke and create a new one.
• Tokens expire after 90 days.You’ll see the expiry date on the tokens list; rotate before then.
• Revoke any token instantly from the tokens page in Settings. Revocation takes effect on the next authenticated request — typically within a few minutes.
• Every MCP call is logged with the token id, tool name, status, and duration. If you suspect a compromised token, revoke it immediately and contact support.