Agent access to RankSage · OAuth 2.0 (PKCE) or personal access token

RankSage inside your agent, read-only.

The RankSage MCP server exposes your visibility, content, competitor, behaviour, traffic and action-queue data as read-only tools inside Claude, Claude Code, Cursor and any other MCP-capable agent. Streamable HTTP transport, OAuth 2.0 with PKCE and dynamic client registration, or a scoped personal access token.

How RankSage works

What it provides

What MCP server gives RankSage.

Read-only tools over the whole product — visibility summary and detail, search analytics, traffic, content report, gaps, competitors, behaviour, site readiness and the action queue.

Streamable HTTP transport with OAuth 2.0 (PKCE, dynamic client registration) or personal access tokens.

Scoped tokens: nothing writable, and conversation access is opt-in per token.

Setup

How to connect.

Add the server to your agent

Point it at the MCP endpoint published on the developers page.

Authorise

OAuth in the browser, or paste a personal access token created in RankSage under Settings → MCP.

Ask

Call tools like get_visibility_summary, list_gaps or list_action_queue from inside the conversation.

What it unlocks

The capabilities it feeds.

RankSage in your editor

Read-only tools inside Claude, Claude Code and Cursor over scoped tokens. Nothing writable, by construction.

Agent Readiness

robots.txt, llms.txt, agents.md and your structured data — whether AI agents can reach you at all, and what to publish if not.

One ranked queue

Playbooks, recommendations and tasks merged into one what-do-I-fix-next list, ordered by a weighting you can read.

Limits

What it does not do.

Every tool is read-only and tenant-bound server-side — no request can name another account.

Conversation-history tools are off unless a token is created with that scope.

FAQ

Questions about MCP server, answered.

What it provides, what it needs, and where its edges are.

Any MCP client that speaks Streamable HTTP — Claude, Claude Code and Cursor are tested. The OpenAPI spec and server card on the developers page describe the endpoint and auth for anything else.

No. Every exposed tool is read-only; the server has no write operations.

See every integration

EARLY ACCESS

Start with the two that matter.

Google Analytics and Search Console, read-only, about five minutes. Add MCP server whenever it earns its place.