Which transport does the server use?
Streamable HTTP at https://reachsurge.ai/api/mcp/mcp. OAuth 2.1 with PKCE for interactive clients, or a bearer API key for headless use.
Setup guide
The ReachSurge connector is a standard Model Context Protocol server over streamable HTTP. Any MCP-compatible client can connect with OAuth 2.1 (interactive sign-in) or a ReachSurge API key (Authorization header).
Requires a ReachSurge Growth plan or higher · Read-only by default · API-key auth
Use the streamable-HTTP transport with this URL. OAuth-capable clients discover the authorization server automatically via the standard .well-known metadata.
MCP endpoint (streamable HTTP)
https://reachsurge.ai/api/mcp/mcpInteractive clients: complete the OAuth 2.1 + PKCE sign-in with your ReachSurge email. Headless clients: create an API key in Settings → API and send it as a bearer token:
HTTP header
Authorization: Bearer rs_live_YOUR_KEYCall list_sites first to get website IDs, then any of the read tools — get_citation_overview, get_share_of_voice, get_authority_score, get_analytics, get_traffic_forecast, and more.
Streamable HTTP at https://reachsurge.ai/api/mcp/mcp. OAuth 2.1 with PKCE for interactive clients, or a bearer API key for headless use.
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.
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.
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.
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.
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.
Full connector reference — tools, security, troubleshooting — in the help center.