Google Search Console MCP Server for Claude and ChatGPT

Connect your Google Search Console property to Claude or ChatGPT through SourcetoMCP. Analyse clicks, impressions, CTR and average position, compare performance over time, and inspect Google's recorded indexing status for individual URLs.

Read-only access to your property, with the dates, dimensions and source data returned alongside each report.

Agent asks

Which pages lost clicks over the last 28 days?

/guides/keyword-research: 600 → 420 clicks across two 28-day periods. Down 180 clicks (30%).

Agent asks

Has Google processed our sitemap?

/sitemap.xml: processing complete, 511 submitted URLs, 3 warnings and 0 errors.

Why Search Console data matters for your agent

Search Console reports how your property appears in Google Search. Your agent can compare queries and pages, examine changes in clicks, and check recorded indexing information.

  • Use Google's first-party search data. See clicks, impressions, CTR and average position for your connected property.
  • Query and page-level detail means real answers. Your agent can point at exactly which pages to fix, instead of reporting a vague traffic number.
  • Indexing status catches problems early. Inspect a URL's recorded coverage state and last crawl time when investigating indexing issues.

How it works

1

Connect Search Console. Sign in with Google, approve read-only access, and select your Search Console property.

2

Your agent asks in plain language. It calls the right MCP operation behind the scenes and gets real clicks, impressions, rankings, or indexing status back.

3

Every answer shows its work. Structured data comes back with the exact dimensions and filters used, so you can see how the answer was built rather than take it on faith.

Search performance

by query · last 28 days · sample data

QueryClicksImpr.Pos.
mcp server for ai agents2143,1024.2
connect search console to claude961,8456.1
ai agent data access589028.7
See it work

Ask about your search performance. Get real data back.

master — ✳ Claude Code — claude — 120×30
Claude Code v2.1.224
Sonnet 5 · Claude Pro
/Users/master
Search Console connected · Read-only
| Using Sonnet 5 (from .claude/settings.json) · /model
  +1 more · /status
❯
master Sonnet 5
‖ manual mode on
What's included

Built for real answers, beyond raw numbers

clicks · impressions

Search performance by query, page and more

Break clicks, impressions, CTR, and position down by date, query, page, country, device, or search appearance, up to three at once.

sitemaps

Sitemap health at a glance

Check submitted URL counts, processing status, and warning and error counts for each sitemap. Google no longer provides indexed URL counts through its Sitemaps API.

index status

Inspect Google’s indexed version of a URL

Check Google’s recorded indexing status, selected canonical and last crawl time for one URL. This uses the version in Google’s index and does not run a live test of the page.

properties

Every property you can access

List every site your connected Google account can see, with permission level, including ones you have never selected as a connection.

5 filters

Filter without a spreadsheet

Up to five filters per query (equals, contains, regex) so your agent narrows straight to the rows that matter.

read-only

Read-only, always

Every Search Console operation only ever reads data. Nothing your agent asks can change a setting or delete anything.

Real prompts teams run against Search Console

Every SourcetoMCP account gets these in the Prompt Library, ready to run against your own connected property.

Performance & rankings

  • Search Console Performance Overview
  • Keyword Ranking Analysis
  • Top Pages Performance Report

Indexing & sitemap health

  • Search Console Indexing Status Check
  • Sitemap Optimisation Report

Ask anything else

Your agent can call these operations directly too. The library is a starting point.

Search Console MCP FAQ

Common questions from teams connecting Search Console to an agent.

Clicks, impressions, CTR and average position by date, query, page, country, device or search appearance, plus sitemap processing information and recorded URL inspection results. Search Console can return a subset of rows. SourcetoMCP returns up to 1,000 rows per performance request, so a result may not include every query or page.

Claude, ChatGPT, Cursor, or any MCP-compatible client. Connect once from your dashboard's "Connect an agent" page and every tool you've paired can use it.

No. Connecting uses Google's own OAuth sign-in. SourcetoMCP never sees your password, and you can revoke access from your Google account at any time.

Search performance history is available for roughly 16 months. Recent data can be incomplete, and the available history depends on your property. URL inspection reports Google’s recorded state for the individual URL.

No. Every Search Console operation is read-only. There's no write or manage operation for this connector.

Search Console is available on every paid plan. See Pricing for how many connections each plan includes.

Securely connect your Google Search Console to AI chat agents.

Connect your first source in minutes.