Skip to content
RankTwig
Log inStart free
RankTwig MCP · Live

Your search evidence, inside the AI conversation.

Connect once. Your AI can ask RankTwig for the authorized site, page and query evidence behind the answer.

Open MCP Server See what to ask
ChatGPT OAuth ready
What this changes

Stop rebuilding SEO context in every chat.

Instead of filtering reports and pasting numbers into a blank conversation, the client can call RankTwig for the evidence it needs.

Why did my pricing page lose clicks?
The click loss is concentrated in four queries.
Impressions stayed broadly stable and average position changed only slightly, so inspect click performance and snippet intent first.
Show me the evidence first.
I can pull the page, query set and comparison window before recommending a change.
Easiest setup

Connect ChatGPT with OAuth.

No RankTwig MCP key copying is required for the ChatGPT OAuth path.

https://ranktwig.com/mcp
01

Open ChatGPT MCP / app setup

Create a custom remote MCP connection.

OAUTH
02

Use the RankTwig endpoint

Enter https://ranktwig.com/mcp and choose OAuth authentication.

OAUTH
03

Sign in to RankTwig

ChatGPT opens RankTwig’s authorization flow. Your signed-in RankTwig account determines workspace access.

OAUTH
04

Allow the connection

Review the consent screen. RankTwig still enforces your plan, membership and safety boundaries.

OAUTH
05

Ask naturally

Try “What should I work on today?” or “Why did this page lose clicks?”

OAUTH
Key-based clients

VS Code and compatible clients still work.

OAuth sits alongside the existing scoped-key path. Read-only and Read + run keys remain independently revocable.

01

Create a scoped MCP key

Dashboard → MCP Server. Choose Read only or Read + run. Copy the key when it appears.

SCOPED KEY
02

Add RankTwig to your client

Use the remote MCP endpoint and keep the raw key in the client’s secure secret prompt.

SCOPED KEY
03

Start the server

Confirm the client can discover the capabilities allowed by the key.

SCOPED KEY
04

Ask from agent chat

The client can request evidence or start the workflows your key is allowed to run.

SCOPED KEY
VS Code configuration

Keep the secret out of the JSON.

The input variable makes VS Code prompt for the RankTwig key instead of storing the raw credential directly in the configuration file.

{
  "inputs": [{
    "type": "promptString",
    "id": "ranktwig-key",
    "description": "RankTwig MCP key",
    "password": true
  }],
  "servers": {
    "ranktwig": {
      "type": "http",
      "url": "https://ranktwig.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:ranktwig-key}"
      }
    }
  }
}
What connects

Read evidence. Run work. Follow it through.

MCP does not bypass RankTwig’s normal authorization, quotas or evidence rules.

01

Read

Ask about site performance, pages, queries, declines and current opportunities without copying data between tools.

WORKSPACE EVIDENCE
02

Run

Start supported Investigator, Page Battle and Brief workflows when the connection has run access.

ESTIMATE FIRST
03

Follow up

Check durable operation status later instead of accidentally starting expensive work twice.

OPERATIONS
04

Stay scoped

Google Search Console and BYOK provider credentials remain inside RankTwig; the MCP client receives authorized RankTwig results, not those secrets.

SECURITY
Ready

Ask the SEO question you were going to ask anyway.

The difference is that the conversation can now reach the RankTwig evidence behind your site.

Open MCP Server Explore use cases