Build on RankSage. MCP first.
The programmatic surface is a read-only MCP server over the whole product, plus the OAuth 2.0 flow that authorises it. Everything on this page has a machine-readable twin, so an agent can integrate without a human reading any of it.
One server, 17 read-only tools.
A Model Context Protocol server speaking Streamable HTTP. It works out of the box in Claude, Claude Code and Cursor: add the server URL and the client discovers the OAuth flow from the published metadata. Every tool is tenant-bound server-side, so a token can only ever read its own account.
Server URL: https://api.ranksage.com/api/v1/mcp Transport: streamable-http Auth: OAuth 2.0 (PKCE S256, dynamic registration) or personal access token
The cross-surface RankSage digest: visibility, traffic, content and action highlights for a period.
AI visibility summary — citation rates and share of voice across the tracked answer engines.
Per-engine, per-prompt AI visibility detail with run history.
AI performance rollup — AI-referred traffic joined to visibility.
Classic search analytics: Search Console queries, top pages and PageSpeed.
GA4-derived traffic summary with engagement metrics.
Content quality scores, E-E-A-T and citability per crawled page.
Content production status — briefs, drafts and optimizer runs.
Content gap counts versus tracked competitors.
Content gaps with the competitor evidence behind each.
Competitor crawl scores, rank matrix and citation benchmarks.
Forum/Reddit SERP presence and community mentions.
Visitor behaviour: frustration signals, heatmap and session rollups.
Technical + agent readiness checks for the connected site.
The ranked action queue merging recommendations across surfaces.
List recent RankSage assistant conversations.
Read one stored assistant conversation.
OAuth 2.0 with PKCE, scoped tokens.
Authorization-code with mandatory PKCE (S256) and RFC 7591 dynamic client registration, so there is no manual credential issuance. Headless agents can use a personal access token created in the app (Settings → MCP), scoped at creation and stored hashed.
- mcp
Read-only access to every core RankSage MCP tool: visibility, content, competitors, behaviour, traffic and the action queue. No write operations exist on this surface.
- conversations
Read stored RankSage assistant conversations. Grantable only to personal access tokens created in the RankSage app with explicit consent — OAuth grants cannot carry this scope.
The full walkthrough, written for agents, is at /auth.md.
Every file this domain publishes, at its standard path.
Versioning and deprecation
The API is versioned in the URL path (/api/v1). Breaking changes ship as a new path version, never in place; when a version is scheduled for retirement, the deprecation is announced on this page and in the OpenAPI spec with at least 90 days of overlap in which both versions work. Additive changes (new tools, new optional fields) arrive within the current version.
The API itself is read-only and rate-limited; there are no write endpoints on the agent surface. Questions or something broken? hello@ranksage.com, or the contact page.
Your AI-visibility data, inside your agent.
Connect the MCP server and ask your assistant what changed this week, with numbers traceable to stored runs.
No payment details. One email when access opens.