Data & Analytics

Google Search Console

Pull GSC search performance data, keywords, and pages.

Works with: Claude DesktopClaude CodeCursor
Quick install
npx -y gsc-mcp-server

How to install the Google Search Console MCP server

Add this to your Claude Desktop MCP configuration:

{
  "mcpServers": {
    "search-console": {
      "command": "npx",
      "args": [
        "-y",
        "gsc-mcp-server"
      ]
    }
  }
}

Add this to your Claude Code MCP configuration:

npx -y gsc-mcp-server

Add this to your Cursor MCP configuration:

{
  "mcpServers": {
    "search-console": {
      "command": "npx",
      "args": [
        "-y",
        "gsc-mcp-server"
      ]
    }
  }
}

The Search Console MCP server gives Claude direct access to your GSC data. Search performance reports, URL indexing status, sitemap submissions, and quick-win analysis. For anyone doing SEO, this is the highest-leverage install you can run alongside GA4.

GSC’s UI is good for individual queries but slow for multi-step analysis. The MCP server flips the dynamic: ask the question once, let Claude run the right API calls.

Why use it

The most useful SEO analysis happens when you can join queries across time, pages, and intent. “Which queries used to convert and have dropped off?” is hard in the GSC UI but easy as a prompt. “What pages have impressions but low CTR, and how do I improve them?” is the exact question Claude can answer in seconds with the MCP server installed.

For solo founders running SEO without a dedicated team, this is the closest thing to having a search analyst on call.

What it actually does

Search analytics: query impressions, clicks, CTR, and position by query, page, country, or device. Filter by date range, search type (web, image, video), and search appearance. URL inspection: check indexing status for a specific URL. Sitemaps: list, fetch status, and submit. Some servers also expose enhanced “quick win” helpers that detect specific opportunity patterns (page-2 queries, falling rankings, indexing failures).

Practical patterns:

  • “Find every query I rank in positions 5-15 that has more than 50 impressions a month.”
  • “Why has /pricing dropped from position 4 to 9? Show me the click and impression history.”
  • “Inspect this URL and tell me if it’s indexed and what date Google last crawled it.”

Gotchas

Data is delayed by 2-3 days. The Search Console API returns the same data the UI does, with the same delay. Don’t trust “today” or “yesterday” numbers; lag is real.

Permissions matter. The OAuth flow only sees properties your account has access to. If you’re managing client sites, make sure the account you authenticate with is added to each property.

Pair with GA4 for the full SEO loop: GSC for what people searched, GA4 for what they did after they landed. Add Brave Search or Exa for live competitor research and you have a complete SEO research stack inside Claude.

For ContextBolt-style workflows where you save SEO articles and case studies as you read them, ContextBolt plus GSC is genuinely powerful: Claude can correlate what you’ve been learning with what’s happening on your own site.

MCP servers related to Google Search Console

All in Data & Analytics →

PostgreSQL

Anthropic's official Postgres server with read-only schema and queries.
S

SQLite

Anthropic's official SQLite server for local databases.

Supabase

Query Supabase Postgres and storage via the official server.
B

BigQuery

Query Google BigQuery datasets via the official Google MCP.

Google Search Console MCP server: FAQs

Is the GSC server official?

No. Google hasn't shipped a first-party Search Console MCP. The community implementations wrap the Search Console API and cover the main use cases (search performance, URL inspection, sitemaps).

What does it need to authenticate?

OAuth from a Google account that has access to the Search Console properties you want to query, or a service account that's been added as a delegated user in the property settings. Service accounts are usually easier.

What's the right URL format for queries?

Use the full URL with the trailing slash, e.g. https://contextbolt.com/. Avoid sc-domain: prefixes for Search Console queries; the API returns different shapes depending on the property type and most servers assume URL-prefix properties.

Can it inspect indexing status?

Yes. The URL Inspection API endpoint is exposed by most servers. You can ask Claude to check whether a specific URL is indexed, the last crawl date, and any reported issues.

Will it surface keyword opportunities automatically?

Some servers expose 'quick win' helpers that find queries ranking on positions 5-15 with decent impressions. Otherwise, Claude can write the query itself: just ask 'find queries on page two that I should optimise for'.

Back to all MCP servers