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 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:

claude mcp add --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.

3. Available tools

Your token has access to 50tools, 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.

Limits

• 200 requests per minute per token (shared with all tool calls).
• 80 direct messages per day across your LinkedIn accounts.
• 40 enrichment calls per day (applies to AI recommendations and campaign enrichment).
• Invitations are not sent directly via MCP. They flow through campaign automation, which is capped at 100 new invitations per LinkedIn account per week.

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

Privacy & security

• Tokens are scoped to your organization. A token issued by you can only read or modify data your own login can see.
• 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.