Connect to Claude (MCP)

Overview

ReachSurge ships a Model Context Protocol (MCP) connector, so you can connect your account to Claude (and other MCP-compatible AI assistants) and ask questions about your data in plain language: "How are my AI citations trending?", "Which competitors outrank me for this keyword?", "What's my entity-authority score?".

The connector is read-only by default, scoped to your team's data, and available on the Growth plan and above. Quick-start guides per client (Claude, Claude Code, Cursor, ChatGPT, generic) live at /mcp. Endpoint:

https://reachsurge.ai/api/mcp/mcp

Connect from Claude (Cowork / claude.ai)

Customer connections use OAuth 2.1. No API keys to copy.

1. In Claude, open Settings → Connectors → Add custom connector.
2. Enter the URL: https://reachsurge.ai/api/mcp/mcp
3. Claude discovers the sign-in automatically. Approve access on the consent screen.
4. Sign in with the same email you use for ReachSurge (the connection links to your account by verified email).

You can review and disconnect connections any time in Settings → API → Connected apps. Disconnecting blocks access immediately.

Connect from Claude Code (API key)

For terminal / developer use, authenticate with a ReachSurge API key instead of OAuth:

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

Create a key in Settings → API. Keys created in the dashboard are read-only. Write access exists in the API but there is no control to enable it yet, so the generate_page tool below is not currently usable from the connector. The read tools all work.

Tools

Read (default):

• list_sites: list your websites (call this first to get website IDs)
• get_ai_citations: recent AI-engine citations (ChatGPT, Claude, Google Gemini, Grok, Perplexity)
• get_citation_overview: totals, linked vs unlinked, per-engine breakdown, daily trend
• get_share_of_voice: competitor share-of-voice per keyword and engine
• get_authority_score: entity-authority score (0–100) with component scores and history
• get_analytics: first-party traffic (pageviews, visitors, AI-referred visits)
• get_gsc_metrics: Google Search Console daily totals (impressions, clicks, CTR, position)
• get_ga4_metrics: GA4 per-page metrics (sessions, pageviews, engagement, bounce)
• get_traffic_forecast: 30-day traffic forecast with confidence bounds
• list_pages: generated-page inventory with quality scores
• get_job: check the status of an async job (e.g. from generate_page)

Write (not currently reachable, see the note above):

• generate_page: queue AI generation of SEO/GEO pages for target keywords (charges your page quota)

Security & privacy

• OAuth 2.1 + PKCE, tokens are scoped and audience-bound to the ReachSurge connector.
• Tenant isolation: a connection can only read its own team's data.
• Rate limits & quota: connector traffic shares your plan's API budget; every call is rate-limited.
• Audit log: every tool call is recorded in your tamper-evident audit log.
• Revocable: disconnect any time in Settings → API → Connected apps; access is also removed on downgrade or cancellation.

For exactly what data the connector can access and how it's shared, see our Privacy Policy (§6, "Claude / AI Assistant Connector").

Troubleshooting

• "This account is not authorised to sign in": your AI-assistant sign-in email must match a verified ReachSurge account on a Growth+ team.
• Tools return "insufficient_scope": you're calling the write tool (generate_page), which dashboard-created keys can't authorise yet. Use the read tools, or generate pages from the app.
• 403 plan_required: the connector requires the Growth plan or higher.