Google Search Console MCP Server — SEO analysis for Claude, ChatGPT & Cursor

Self-hosted MCP server for Google Search Console. It syncs your Search Console performance data (clicks, impressions, CTR, positions by query, page, country and device) into a local ClickHouse database and gives AI agents — Claude Code, Claude Desktop, ChatGPT, Cursor, VS Code Copilot, Windsurf — ready-made SEO analysis tools: traffic drop diagnosis, decaying pages, striking-distance keywords, keyword cannibalization, low-CTR snippets, indexing issues and weekly SEO reports.

Run it locally with Docker, upload a Google service account JSON key, and ask your AI:

"Why did my organic traffic drop last week?" · "Find keywords ranking 4–15 I can push into the top 3." · "Which pages are losing clicks?" · "Find keyword cannibalization." · "Create my weekly SEO report."

Contents

• Why this Search Console MCP server

• Quick start (Docker)

• Connect Claude, ChatGPT, Cursor and other AI agents

• MCP tools and prompts

• Configuration

• How it works

• Hosted version (free, 10 sites)

• FAQ

Related MCP server: seoagent

Why this Search Console MCP server

Most Search Console MCP servers are thin wrappers over the Search Console API: the model gets raw rows, hits the 25,000-row and 16-month limits, and has to do the math itself — slowly and often wrongly. This server does the analysis before the model sees the data:

• Answers, not rows. Every tool returns a summary, the evidence and prioritized actions. The model retells deterministic results computed in SQL instead of inventing numbers.

• All your data, locally. Daily import at the finest grain (date × query × page × country × device), including a reconciled row for anonymized queries so totals match Search Console exactly.

• History beyond 16 months. Search Console forgets data after 16 months; your local copy doesn't.

• Fast. ClickHouse answers year-over-year comparisons across millions of rows in milliseconds.

• Private. Your data never leaves your machine except for the calls to Google's API and to the AI you choose.

• Works with every MCP client. Streamable HTTP (http://localhost:3333/mcp) and stdio.

Quick start (Docker)

Requirements: Docker with Compose, a Google account with access to Search Console.

git clone https://github.com/ozhehkovski/google-search-console-mcp.git
cd google-search-console-mcp
docker compose up -d

1. Create a service account key — step-by-step guide (5 minutes, free): enable the Search Console API in Google Cloud, create a service account and download its JSON key.

2. Upload the key at http://localhost:3333 (or save it as credentials/service-account.json).

3. Add the service account email shown on that page as a user in Search Console → Settings → Users and permissions for each site (the Restricted permission is enough), then click Sync now.

4. Connect your AI agent (below) and ask a question. The latest weeks are imported first, so answers are available within minutes while the rest of the 16-month history keeps loading.

Want to try it without a Google key? Load a synthetic demo site:

docker compose exec gsc-mcp node dist/index.js demo

Connect your AI agent

The MCP endpoint is http://localhost:3333/mcp (Streamable HTTP). The status page at http://localhost:3333 shows ready-to-copy snippets.

Claude Code

claude mcp add --transport http search-console http://localhost:3333/mcp

Cursor — ~/.cursor/mcp.json, Windsurf — ~/.codeium/windsurf/mcp_config.json (use serverUrl):

{
  "mcpServers": {
    "search-console": { "url": "http://localhost:3333/mcp" }
  }
}

VS Code (GitHub Copilot) — .vscode/mcp.json:

{
  "servers": {
    "search-console": { "type": "http", "url": "http://localhost:3333/mcp" }
  }
}

Claude Desktop — claude_desktop_config.json (stdio through the running container):

{
  "mcpServers": {
    "search-console": {
      "command": "docker",
      "args": ["exec", "-i", "gsc-mcp", "node", "dist/index.js", "stdio"]
    }
  }
}

Claude.ai and ChatGPT (web) connect only to public HTTPS servers with OAuth. Use the hosted version, or put this server behind your own HTTPS reverse proxy.

If you expose the server beyond localhost, set MCP_AUTH_TOKEN and send Authorization: Bearer <token> (for Claude Code: --header "Authorization: Bearer <token>").

MCP tools

CTR expectations are calibrated on your site's own data (median CTR by position), falling back to an industry curve where there isn't enough volume.

MCP prompts

Ready-made workflows your MCP client shows as commands: weekly_seo_report, investigate_traffic_drop, striking_distance_sprint, cannibalization_cleanup, content_refresh_plan, indexing_audit.

Configuration

Copy .env.example to .env; every variable is optional.

Useful commands:

docker compose exec gsc-mcp node dist/index.js sites   # properties the service account can read
curl -X POST http://localhost:3333/api/sync            # import missing days now (same as "Sync now")
docker compose logs -f gsc-mcp                         # sync progress

How it works

Google Search Console API ──(service account, read-only)──► sync (every 6 h)
                                                               │  date × query × page × country × device
                                                               ▼
AI agent ──MCP (HTTP / stdio)──► tools ──SQL──► ClickHouse ◄───┘
               ▲                   │
               └─ summary + evidence + actions (analysis in TypeScript, unit-tested)

• src/sync — incremental import: only missing days are requested, newest first; an interrupted day is cleaned up and imported again.

• src/db — ClickHouse schema and parameterized analytical queries.

• src/analysis — pure, tested SEO logic: change-point detection, cause attribution, CTR curve calibration, decay classification, cannibalization and flip-flops, action plan scoring, report rendering.

• src/mcp — MCP tools and prompts.

Local development:

pnpm install
pnpm test          # unit tests
pnpm typecheck
docker compose up -d clickhouse   # add `ports: ["127.0.0.1:8123:8123"]` to the clickhouse service first
CLICKHOUSE_URL=http://localhost:8123 CLICKHOUSE_USER=gsc CLICKHOUSE_PASSWORD=gsc-local-password pnpm dev

Hosted version

my.topify.pro runs the same analysis as a managed MCP server:

• Free, up to 10 sites per user.

• Sign in with Google — no Google Cloud project, service account or Docker.

• Works with Claude.ai, Claude Desktop, ChatGPT (OAuth connectors) and API keys for Claude Code, Cursor and VS Code.

• MCP endpoint: https://my.topify.pro/api/mcp.

FAQ

Is this an official Google product? No. It uses the public Search Console API with read-only access.

Which Search Console data is available? Search performance (Search Analytics) by query, page, country and device; URL Inspection results for the most important pages; sitemaps. Search Console reports data with a 2–3 day delay, and every analysis period ends on the last day with data.

Why a service account instead of "Sign in with Google"? It runs unattended on your machine, needs no OAuth app verification and only gets the properties you explicitly share with it.

How much data can it handle? ClickHouse comfortably handles tens of millions of rows on a laptop. The import follows Search Console API quotas; very large sites take longer on the first run.

Does my data leave my computer? Only the tool results you ask your AI agent about are sent to that AI provider.

Can I use it with ChatGPT? ChatGPT connectors need a public HTTPS URL with OAuth — use the hosted version or your own HTTPS proxy.

License

MIT © Topify. Contributions welcome — open an issue or a pull request.

Keywords: Google Search Console MCP, GSC MCP server, Search Console API, SEO MCP server, Model Context Protocol, Claude SEO, ChatGPT SEO, Cursor MCP, AI SEO agent, organic traffic drop analysis, keyword cannibalization, striking distance keywords, self-hosted SEO analytics, ClickHouse, Docker.