The short answer
Google has not published an MCP server for Search Console. It has official ones for Google Analytics and Google Ads, but for Search Console you pick between an open-source server you run yourself and a hosted connector from another company.
They all read the same Search Console API, so they share its limits. The biggest one: Google only names part of your searches. On our own site it named the search for 56% of impressions. No server can show the other 44%.
- 56% search shown
- 44% search hidden by Google
See the numbers
| Impressions | Share |
|---|---|
| Search shown | 56% |
| Search hidden | 44% |
| All impressions (658) | 100% |
Data: Harvv, our own Search Console
That share is different on every site, and it matters when an AI adds things up. If it sums the searches it can see and calls that your total, the answer is too low. Your page totals do include the hidden searches, so the two numbers won't match, and that's normal.
Is there an MCP for Google Search Console?
Not from Google, as of November 11, 2026. Google's developer sites describe an official server for Google Analytics and one for Google Ads. We found none for Search Console. What exists comes in three kinds:
- Open-source servers you run yourself. Free, and your Google sign-in stays on your computer. The most-starred one we found is mcp-gsc on GitHub.
- Hosted connectors. A company runs the server and you sign in with Google on its page. Quick to set up and they work in claude.ai and ChatGPT, but that company then holds access to your Search Console.
- Tools with Search Console built in. Analytics products that connect Search Console next to their own data and offer one MCP for all of it. Harvv is one of these.
How do you connect Google Search Console to Claude?
For an open-source server, the steps look like the ones for Google's Analytics server. These are from the mcp-gsc README:
- Create a Google Cloud project and turn on the Google Search Console API.
- Create an OAuth client of type "Desktop app" in that project and download its JSON file.
- Install uv, the Python tool the server runs with.
- Add the server to your AI app's config, with the path to that JSON file. The README has examples for Claude Desktop and Cursor.
- Ask a first question. A browser window opens for the Google sign-in. Check that the consent screen says "View Search Console data", not "View and manage".
For a hosted connector, you add its web address in Claude under Settings, then Connectors, and sign in with Google on the company's page.
What should you check before you sign in?
- Read-only or full access. Search Console has two permission levels. Read-only can't change anything. Full access can add or remove sites and sitemaps. In the code of mcp-gsc, 21 tools are defined, read-only is the default, and the 3 tools that add a site, delete a site or delete a sitemap stay off unless you turn on a setting.
- Who holds the sign-in. With a server on your computer, you do. With a hosted connector, the company does. Read its privacy page, and remove its access in your Google account when you stop using it.
- How many rows it asks for. In mcp-gsc the main search tool returns 20 rows unless the AI asks for more. An answer built on the top 20 searches can miss most of a site. Ask the AI how many rows it read.
What limits do they all share?
- Hidden searches. The chart above. It comes from Google, not from the server.
- Top rows only. One request returns at most 25,000 rows (Google's API reference), and Google returns the top rows, not all of them. Large sites need several requests.
- 16 months of history. Search Console keeps no more than that.
- Page checks are capped. Asking Google whether a page is indexed is limited to 2,000 checks a day for each site (Google's limits page). Fine for a few pages, slow for a whole site.
- Clicks stop at the click. Search Console knows someone clicked. It doesn't know what they did on the page.
Where Harvv fits
Harvv asks for read-only access and copies your searches and pages each day, up to 25,000 searches. Its answers state the named share, so an AI doesn't treat the visible searches as the whole picture. And because Harvv's own script is on your pages, it can say what people did after the click.
It doesn't do everything an open-source server does. It reads a fixed set of reports. It asks Google which of your pages are indexed once a week, for up to 200 pages from your sitemap, not on demand. If you need a custom report or an index check right now, run an open-source server next to it.
For the same comparison across Google Analytics, Google Ads, Meta Ads and Clarity, see our guide to SEO and marketing MCP servers.
How we checked this
- "No official server" means a search on November 11, 2026 found none from Google. That could change, and we'll update this page when it does.
- The mcp-gsc numbers were counted from its source code on GitHub the same day. We read the code. We did not install or run it, so we can't say how it behaves in use.
- The 56% is our own site's Search Console for Oct 14 to Nov 9, 2026, 658 impressions. It's one small site. Yours will differ.
- Google's limits are quoted from its Search Console API pages.