Skip to main content

Setup guide

Connect ReachSurge to Claude Code in one command

For terminal and developer workflows, add ReachSurge to Claude Code with an API key. You can then ask Claude Code about your AI citations, analytics, and forecasts — or wire ReachSurge data into your own automation.

Requires a ReachSurge Growth plan or higher · Read-only by default · API-key auth

  1. 1

    Create a ReachSurge API key

    In ReachSurge, go to Settings → API and create a key. A standard key is read-only; enable write access when creating it only if you want the assistant to generate pages with the generate_page tool.

  2. 2

    Add the MCP server

    Run this in your project (or with --scope user to make it available everywhere), replacing the placeholder with your key:

    Terminal

    claude mcp add reachsurge --transport http https://reachsurge.ai/api/mcp/mcp \
      --header "Authorization: Bearer rs_live_YOUR_KEY"
  3. 3

    Query your data

    Start a Claude Code session and ask "List my ReachSurge sites", then "Get my citation overview for the last 30 days". Tools appear under the reachsurge server name.

Not on Growth yet? The MCP connector is included on Growth and Enterprise plans. See pricing or start with a free preview.

Frequently asked questions

Should I use an API key or OAuth in Claude Code?

Claude Code connects with a ReachSurge API key via the Authorization header. OAuth sign-in is the flow for claude.ai and other chat clients; keys are simpler for terminal use and can be scoped read-only or write.

Is the ReachSurge MCP connector read-only?

Yes, by default. OAuth connections and standard API keys can only read your data (citations, analytics, scores, forecasts). The single write tool — generate_page — requires an API key created with write access explicitly enabled in Settings → API. Checking job status with get_job is a read and works on any connection.

Which ReachSurge plan do I need?

The MCP connector is available on the Growth plan and above. OAuth sign-ins from accounts on lower plans are rejected with a 403 plan_required error, and API keys can only be created on Growth and Enterprise teams.

What data can the assistant access?

Only your own team's data: AI citations, citation overview, share of voice, authority score, first-party analytics, Google Search Console and GA4 metrics, traffic forecasts, and your site and page inventory. Connections are tenant-isolated and every tool call is recorded in your tamper-evident audit log.

How do I disconnect or revoke access?

In ReachSurge, go to Settings → API → Connected apps and disconnect the connection; access is blocked immediately. API keys can be deleted in Settings → API. OAuth access is also removed automatically on plan downgrade or cancellation. If you downgrade between paid plans, existing API keys keep working at the lower plan's rate limits (delete them if that's not intended); if you cancel entirely, they stop working.

Does connector usage count against my plan limits?

Connector traffic shares your plan's API budget and is rate-limited per call. The generate_page write tool charges your normal page-generation quota, exactly as if you generated the page from the dashboard.

Connect from other clients

Full connector reference — tools, security, troubleshooting — in the help center.