MCP Connector
ReachSurge ships a hosted Model Context Protocol (MCP) server. Connect it to Claude, ChatGPT, Claude Code, Cursor, or any MCP client and ask in plain language: “How are my AI citations trending?”, “What's my share of voice against competitors?”, “Forecast my traffic for the next 30 days.” The assistant answers from your live ReachSurge data.
Endpoint · streamable HTTP · OAuth 2.1 or API key
https://reachsurge.ai/api/mcp/mcpStep-by-step guides per client, OAuth for chat assistants, API keys for developer tools.
ReachSurge + Claude
OAuth sign-in, no API keys · 3 steps
ReachSurge + Claude Code
API-key setup · 3 steps
ReachSurge + Cursor
API-key setup · 3 steps
ReachSurge + ChatGPT
OAuth sign-in, no API keys · 3 steps
ReachSurge + Any MCP client
API-key setup · 3 steps
Every tool is scoped to your team's data and audited. Read tools work with any connection; the one write tool (generate_page) requires an explicitly write-scoped API key.
get_ai_citations
Recent AI-engine citations across ChatGPT, Perplexity, Claude, Google Gemini, and Grok
get_citation_overview
Citation totals, linked vs unlinked, per-engine breakdown, and 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, and 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_sites
List your websites (call this first to get website IDs)
list_pages
Generated-page inventory with quality scores
generate_pagewrite
Queue AI generation of SEO/GEO pages for target keywords (charges your page quota)
get_job
Check the status of an async job, e.g. from generate_page — read-only, works on any connection
OAuth connections and standard API keys can't change anything. Write access is a separate, explicit key scope.
A connection reads its own team's data only. Disconnect instantly from Settings → API → Connected apps.
Each tool call is rate-limited and recorded in your tamper-evident audit log.
A hosted Model Context Protocol (MCP) server that exposes your ReachSurge data — AI citations across five engines, share of voice, authority score, analytics, and traffic forecasts — as tools any MCP-compatible AI assistant can call. You ask questions in plain language; the assistant reads your live data.
Claude (claude.ai and desktop), Claude Code, ChatGPT (custom connectors via developer mode), Cursor, and any client that speaks MCP over streamable HTTP. Interactive clients sign in with OAuth 2.1; developer tools authenticate with a ReachSurge API key.
The connector is read-only by default and tenant-isolated — a connection can only read its own team's data. Every tool call is rate-limited and recorded in your tamper-evident audit log, and you can revoke access instantly from Settings → API → Connected apps.
Growth and Enterprise. Connector traffic shares your plan's API budget, and the optional generate_page write tool charges your normal page-generation quota.
Not with a default connection. OAuth connections and standard API keys are read-only. Only an API key created with write access enabled can queue page generation (generate_page) — nothing else on the surface writes.
Track citations across ChatGPT, Perplexity, Claude, Google Gemini, and Grok — then query it all from your assistant. Full connector reference.