Google Search Console MCP: Query GSC Data With AI (2026 Guide)

Google Search Console holds some of the most actionable SEO data available — which queries drive impressions, which pages are losing clicks, which URLs have indexing errors, whether your sitemap was processed. The problem is that getting answers out of it means navigating a dated interface, downloading CSVs with 1,000-row limits, and cross-referencing multiple reports manually.

A Google Search Console MCP server removes that friction entirely. It connects AI assistants like Claude directly to your GSC account, so you can query your search performance data, inspect URLs, check sitemap status, and identify SEO opportunities through plain-language conversation.

This guide explains what a Google Search Console MCP server is, what it can do, how different implementation options compare, and how WordPress site owners can connect GSC to Claude in minutes using Easy MCP AI.

What Is a Google Search Console MCP Server?

A Google Search Console MCP server is an implementation of the Model Context Protocol that connects AI clients to the Google Search Console API. Once connected, the AI can retrieve search analytics data, check indexing status, manage sitemaps, and inspect individual URLs — all through natural language queries.

The Model Context Protocol is an open standard that Anthropic released on November 25, 2024, and donated to the Linux Foundation’s Agentic AI Foundation on December 9, 2025. The protocol is now supported by Claude, Cursor, VS Code, n8n, ChatGPT, and most major AI platforms. A single GSC MCP server works with all of them.

There is no single official Google Search Console MCP server from Google (unlike GA4, where Google published an official implementation). The ecosystem has produced several well-maintained open-source and hosted implementations, with toolsets ranging from basic data retrieval to 20+ SEO-focused analysis tools.

What a Google Search Console MCP Server Can Do

Across the major GSC MCP implementations, the core tools fall into four categories:

Search Analytics

Query impressions, clicks, CTR, and average position for any combination of dimensions (query, page, country, device, search type, date range)
Compare periods side-by-side — e.g., last 28 days vs. the same period last year
Filter by specific queries, pages, countries, or devices
Identify queries where you rank in positions 4–10 (“quick wins” — near the top but not quite there)

URL Inspection

Inspect any URL on a verified property for indexing status
Check whether a URL is indexed, excluded, or has crawl errors
Identify the canonical URL Google is using for a given page
See last crawl date and any coverage issues

Sitemap Management

List all sitemaps submitted to a property, with submitted vs. indexed URL counts, errors, and warnings
Get detailed status for any individual sitemap — error count, warning count, and processing state
Check last-submission timestamps and indexing progress

Site and Property Management

List all verified properties in a Search Console account
Retrieve details about specific properties

Some implementations extend these basics with higher-level analysis tools: content decay detection (pages losing clicks over time), keyword cannibalization identification, CTR benchmark comparisons, and alerting for index coverage drops.

How It Works

The GSC MCP server authenticates to the Google Search Console API using either OAuth (user-based) or a service account (server-based). Once authenticated, it exposes its tools via the MCP protocol. The AI client — Claude, Cursor, or any other compatible client — calls these tools in response to natural language prompts, receives structured data, and incorporates it into its reply.

The key difference from the Google Search Console interface:

No row limits — the API returns paginated results without the 1,000-row cap of the GSC data export
Real-time queries — data is fetched live, not from a stale CSV
Multi-step reasoning — Claude can query GSC, identify a pattern, and immediately follow up with a deeper query in the same conversation
Cross-tool analysis — if you also have GA4, SEMrush, or other tools connected, Claude can combine GSC and traffic data in a single answer

Connect Google Search Console to Claude via Easy MCP AI

For WordPress site owners, Easy MCP AI is the fastest way to connect GSC to Claude. Easy MCP AI is a free, open-source WordPress plugin that turns your site into a fully compliant remote MCP server. Google Search Console is one of its built-in external data integrations.

What Easy MCP AI’s GSC Tools Can Do

Easy MCP AI exposes 6 Google Search Console tools alongside its full suite of 204 tools — covering WordPress posts, pages, WooCommerce, SEO, Google Analytics 4, SEMrush, DataForSEO, and more. The GSC integration supports:

Search analytics queries — pull clicks, impressions, CTR, and position for any dimension (query, page, country, device) with custom date ranges and filters
URL inspection — check the index status, canonical, and crawl date for any URL on your site
Sitemap management — list all submitted sitemaps, check submitted vs. indexed counts, and get detailed error and warning breakdowns per sitemap
Site listing — retrieve all properties associated with your Search Console account

Because Easy MCP AI connects GSC and GA4 through the same MCP server, Claude can combine both data sources in a single prompt — for example: “Which pages have high impressions but low sessions in Analytics?” — without switching tools.

All credentials are stored AES-256-GCM encrypted with per-provider HKDF-derived keys on your own WordPress server. Nothing is transmitted to any third party until Claude actively calls a tool that requires it. Easy MCP AI never bills for API usage — it uses your own Google Cloud service account.

Setup: GSC + Claude via Easy MCP AI

Step 1 — Install Easy MCP AI. Install and activate Easy MCP AI from the WordPress plugin directory. It is free with no paid tiers, no usage limits, and no telemetry.

Step 2 — Create a Google Cloud service account. In Google Cloud Console, create a service account and download the JSON key file. Add the service account email as an owner or full user in Google Search Console for your property.

Step 3 — Configure GSC in Easy MCP AI. Go to Easy MCP AI → External Data → Google Search Console in your WordPress admin. Upload the service account JSON and set your default site URL.

Step 4 — Connect to Claude. Copy your MCP server URL from Easy MCP AI → Dashboard. In Claude, go to Settings → Connectors → Add custom connector, paste the URL, and authorize via OAuth.

Step 5 — Start querying. Open a Claude conversation and ask about your search performance. Claude calls the GSC tools in real time and returns structured answers.

Example Prompts After Connecting

“Which queries have more than 500 impressions but a CTR below 2% this month?”
“Show me pages that ranked in positions 4–10 last week — my quick wins.”
“Inspect the URL /blog/my-post and tell me if it’s indexed.”
“List all my sitemaps and how many URLs are indexed in each one.”
“Which pages lost the most clicks compared to the same period last month?”
“List all my sitemaps — which ones have errors or warnings?”

GSC MCP vs. Manual Search Console Workflow

	Google Search Console UI	GSC MCP connection
Row limit	1,000 rows per export	API-paginated, no hard cap
Date range flexibility	Fixed presets or custom picker	Any range in natural language
Cross-report analysis	Requires multiple report views	Single prompt can combine dimensions
URL inspection	One URL at a time in the UI	Batch inspection possible via AI
Sitemap status	Manual check in the UI	List and inspect via AI prompt
Combining with GA4 data	Separate tool, manual cross-reference	Single prompt if both tools are connected
Learning curve	Moderate — multiple tabs and reports	Near zero — ask in plain English

The most impactful difference for most SEOs: multi-step analysis that would normally take 20–30 minutes of clicking across reports can be reduced to a single conversation turn.

Implementation Options Beyond Easy MCP AI

If you are not running WordPress, several other GSC MCP options exist:

mcp-gsc by AminForou — open-source Python implementation on GitHub (~1,670 lines, built with FastMCP). Uses OAuth with auto-cached tokens. Requires Python and a client_secrets.json from Google Cloud.
Suganthans-GSC-MCP (suganthan-gsc-mcp) — npm-based Node.js implementation with 20 SEO analysis tools including quick wins, content decay detection, keyword cannibalization, CTR opportunity analysis, multi-site dashboards, and Indexing API support. Outputs rich interactive dashboards in Claude Desktop. Updated April 2026 to fix an npm package naming conflict.
Composio — hosted connector that integrates GSC into Claude Code, Claude Agents SDK, Cursor, and other clients without running your own server.
Windsor.ai — no-code connector that supports GSC alongside 300+ other data sources, with multi-account support.

For WordPress site owners, Easy MCP AI remains the most integrated option because it combines GSC with GA4, SEMrush, DataForSEO, WooCommerce, and the full WordPress CMS in a single MCP server.

Key Facts

There is no official Google MCP server for Search Console (unlike GA4, which has one at developers.google.com). The ecosystem has produced several well-maintained open-source implementations.
Authentication uses either OAuth (user-based, browser flow) or a Google Cloud service account (server-based, JSON key)
The GSC Search Analytics API returns up to 16 months of historical data
The Search Console API imposes a daily quota per project — typical free tiers are sufficient for SEO research workloads
Easy MCP AI’s GSC integration is free and open source, credentials stored AES-256-GCM encrypted on your own server

Conclusion

A Google Search Console MCP server turns your GSC account into a data source your AI assistant can query live — keyword performance, indexing status, sitemap health, and URL inspection, all through natural language. Instead of navigating multiple reports and exporting CSVs, you ask Claude a question and get a structured, actionable answer.

For WordPress site owners, Easy MCP AI connects GSC, GA4, SEMrush, and your full WordPress workflow through a single MCP server — free, open-source, and requiring no custom code.

→ Get Easy MCP AI from the WordPress plugin directory