Is there an official Google Search Console MCP server? The fastest way to connect it to Claude and ChatGPT

Google does not publish a Google Search Console MCP server, the piece an AI assistant needs to read your Search Console account. You can still ask Claude or ChatGPT about your search traffic in plain words. The quickest way is a hosted server: with HeyMetra you sign in with Google, pick your site and add one address to your assistant, and a few minutes later you can ask which pages lost clicks last month. This guide shows how, what you can ask, and what the do-it-yourself route involves if you would rather build it.

Does Google publish an official Search Console MCP server?

No. Google lists the MCP servers it publishes in its google/mcp repository. On 8 November 2026 the list had servers for BigQuery, Google Maps, several Cloud products and Google Analytics, but none for Search Console, and the Search Central blog has announced none.

Every Search Console MCP server you will find is built by someone else on Google’s public Search Console API. They all read the same data. What differs is how long they take to set up and which assistants can use them.

Connect Search Console to Claude or ChatGPT in a few minutes

HeyMetra runs the server for you. Setup is three steps, all in the browser:

1. Connect your site. In HeyMetra, choose Google Search Console and sign in with the Google account that already sees your site in Search Console. Pick the property.
2. Add HeyMetra to your assistant. In Claude, add https://mcp.heymetra.com/mcp as a custom connector. In ChatGPT, add the same address in developer mode. In Claude Code it is one command.
3. Ask. Type a question the way you would ask a colleague. The assistant picks the report, the dates and the filters.

Everything happens in the browser, and the connection lives in HeyMetra rather than on your laptop. The same connection works in Claude on the web and on your phone, in ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor and Antigravity, and your whole team can use it. Google is asked for read-only access, so nothing in Search Console can be changed through it. Every plan starts with a seven-day free trial.

What you can ask once it is connected

The questions worth asking are the ones that take several filters, two date ranges or a spreadsheet in the Performance report. Here is one in Claude, for an outdoor gear shop:

Claude

Which of our pages with impressions last month are not indexed, and why?

Read Search Console with HeyMetra

I checked the 42 pages with impressions. Two are not indexed. Google crawled /tents/ultralight-2p but chose /tents/ultralight as its canonical, so the two pages likely read as one. /guides/winter-camping-checklist has not been crawled yet. Both are in your sitemap.

Page	Status
/tents/ultralight-2p	Crawled, not indexed
/guides/winter-camping-checklist	Discovered, not indexed

Reply to Claude…

A few more that work well:

• Which pages got more impressions this month but fewer clicks?
• Which searches do we rank 5th to 15th for with real impressions? Those are the cheapest to move into the top three.
• Which two of our pages show up for the same search, and which one gets the clicks?
• Which question-style searches did we appear for this quarter?

Nine of these, with the exact question to ask for each, are in our guide to SEO analysis with Claude and Search Console.

Ask Search Console together with your other accounts

Search Console tells you who found your site. What they did next sits in other accounts. Connected to the same HeyMetra workspace, one question can read both:

• With Google Analytics 4: which pages get search clicks but lose visitors in the first ten seconds.
• With Google Ads: which searches you pay for while already ranking in the top three for free.
• With WooCommerce: which pages from search bring the orders.

An open-source server reads Search Console alone, so these questions need a second server, a second setup and an assistant that can use both.

The other route: open-source servers

If you prefer to run it yourself, the best-known option is mcp-gsc, with about 2,100 stars on GitHub. mcp-server-gsc is a smaller alternative. Both are free and well maintained. Before your first question, each one asks you to:

1. Create a project in Google Cloud Console and switch on the Search Console API.
2. Create OAuth credentials or a service account, download the credentials file, and for a service account add it as a user on your property.
3. Install the server’s runtime on your computer and add an entry with the file path to your assistant’s config file.
4. Repeat it on every computer that should use it, and update the server when it changes.

They also run only where an app can start a program on your computer: Claude Desktop, Claude Code, Cursor and similar tools. Claude on the web and ChatGPT reach servers from their own cloud, so a server on your laptop does not show up there.

Three things to know about Search Console data

These come from Search Console itself, so every server shows them:

• The last two or three days are missing. Google finishes its figures two to three days late. HeyMetra answers from finished days and says which ones.
• Rare searches are hidden. Google leaves out queries very few people typed, so the named searches add up to less than the site’s total clicks.
• AI Overviews are counted with normal results. The API counts AI Overviews and AI Mode inside web search; only Search Console’s own Generative AI report shows them separately.