Google Search Console MCP servers: the free ones, and when you need more

Search Console MCP servers, compared: the free ones worth trying, how they connect, and the three things none of them does.

A Google Search Console MCP server lets an AI assistant such as Claude read your own Search Console data: the searches you appear for, your clicks, impressions and average position. Google doesn’t publish one for Search Console (it does for Google Analytics), so the servers people use are open source. The most popular, AminForou’s mcp-gsc, has about 1,800 stars on GitHub. They’re free, and for asking Claude about the last few months they are often all you need.

This guide covers what they do, the free ones worth trying, how they connect, and the three things none of them does: keep history, check real rankings, or watch competitors. Checked on 29 September 2026.

What a Search Console MCP server does

MCP, the Model Context Protocol, is how an AI assistant uses outside tools. A Search Console MCP server is a small program that sits between the assistant and Google’s Search Console API. You ask a question in plain English, such as “which queries lost clicks this month?”, and the assistant calls the server, which reads your data and hands it back.

What they read varies. The good ones cover search analytics split by query, page, country and device, comparisons between two periods, and in some cases URL inspection and sitemaps.

The free ones worth trying

ServerLicenceGitHub starsWhat it adds
AminForou/mcp-gscMITabout 1,80020 tools: search analytics by page, query, country or device, period comparisons, URL inspection and sitemaps.
saurabhsharma2u/search-console-mcpMITabout 300Search Console plus Bing Webmaster Tools, GA4 and AdSense, with anomaly checks, URL inspection and PageSpeed.
Suganthans-GSC-MCPApache-2.0about 14029 tools built around jobs: quick wins, click-rate gaps, traffic drops, content decay and cannibalisation.
ahonn/mcp-server-gscNone statedabout 270Search analytics up to 25,000 rows, with regex filters.
Stars from GitHub on 29 September 2026. A repository with no licence file isn’t open source in the legal sense, so check before you build on it.

How to connect one

Each server’s README has the exact steps, but they follow the same pattern:

  1. Create a Google Cloud project and switch on the Search Console API.
  2. Give the server a way in: either sign in with your Google account, or create a service account and add its email address as a user on your Search Console property. Restricted access is enough to read search data.
  3. Add the server to your assistant’s MCP settings. In Claude Desktop that’s its configuration file; Claude Code and Cursor have their own.
  4. Restart the assistant and ask it a question about your site.

What they don’t do

They don’t keep history

Most of these servers read Search Console live each time you ask. Google itself keeps 16 months of data, so anything older is gone, and comparing this autumn with the autumn two years ago isn’t possible.

They don’t check rankings

Search Console’s position is an average across every time you were shown, not where you rank today. A query shown once at 2 and ninety-nine times at 40 averages 39.6, a place you never actually held. To know where you stand for a phrase this morning, something has to check Google.

They don’t watch competitors

Search Console only knows about your own site. It can’t tell you who sits above you, or when a new rival appears.

When you need more: ReplaRank

ReplaRank is a self-hosted rank tracker with its own MCP server: 50 tools, five of them for Search Console. It reads Search Console every day and keeps the history, so it grows past Google’s 16 months. It checks real Google rankings for the phrases you choose, watches your competitors on the same results pages, and puts the two side by side: queries you’re shown for but don’t track yet, page-two queries worth a push, and real clicks beside the estimate.

Two honest limits. It reads less of Search Console than the servers above: queries by date, not pages, countries or devices, and no URL inspection. If that detail is what you’re after, use one of them; they run happily side by side. And it’s a local MCP server, so it works in Claude Desktop, Claude Code and Cursor rather than as a web connector.

ReplaRank is $399 once. You pay DataForSEO directly for the rank checks, roughly 1.6¢ each; Search Console costs nothing.

Questions people ask

Is there an official Google Search Console MCP server?

No. As of September 2026 Google publishes an official MCP server for Google Analytics, but not for Search Console. The Search Console servers people use are open source.

Is a Search Console MCP server free?

The open-source ones are. You need a free Google Cloud project with the Search Console API switched on, and a Google account or service account that has access to your property.

Does a Search Console MCP server show my rankings?

Not exactly. Search Console reports an average position across every time you were shown, not where you rank today for a phrase. For real positions you need a rank tracker.

What can I ask Claude once it’s connected?

Things like which queries lost clicks this month, which pages sit on page two, or which queries you’re shown for but rarely get clicked. The answers come from your own Search Console data.

Servers, stars and features checked on GitHub on 29 September 2026. See also: SEO MCP servers compared and Claude for SEO.