Google Search Console MCP servers compared

A Google Search Console MCP server gives an AI assistant such as Claude, ChatGPT, Cursor, or Claude Code access to your Search Console data through tool calls. The options differ in where they run, how they authenticate with Google, which parts of the Search Console API they cover, which clients they document, and what they cost.

This post compares seven: three hosted services and the four most-starred open-source servers we found. CalmSEO, which publishes this blog, is one of the hosted services. Each claim comes from the project's README or product page, linked in its section. Where a source is silent, we mark it as not documented.

Last checked October 2026. These projects change often, so check the linked source before you install one.

Comparison table

"Documented clients" lists the clients each source names or gives setup steps for. Most of these servers also work in other MCP clients. Local servers run as a process on your computer, so they work in desktop and command-line clients such as Claude Desktop, Claude Code, and Cursor. Claude on the web and ChatGPT connect to MCP servers by URL. They need a hosted server or a local one deployed somewhere reachable.

Hosted servers

CalmSEO

CalmSEO is a hosted MCP server at https://mcp.calmseo.com/mcp. You add the URL to your client, sign in to CalmSEO with OAuth, and connect a Google account in the CalmSEO dashboard. CalmSEO requests two Google scopes: webmasters.readonly for Search Console and userinfo.email to show which account is connected.

It has six Search Console tools: list_gsc_sites, query_gsc_search_analytics, get_gsc_top_queries, get_gsc_top_pages, get_gsc_page_queries, and list_gsc_sitemaps. All six are marked read-only in their MCP annotations. There is no URL inspection, sitemap submission, or Indexing API support. The same endpoint also has credit-based tools for keyword search volume, keyword ideas, ranked keywords, live SERPs, and single-page audits.

Setup docs cover Claude, ChatGPT developer mode, and Cursor. In Claude Code, run claude mcp add calmseo --transport http https://mcp.calmseo.com/mcp. The Search Console tools are free on every plan. New accounts get 20 credits for the paid tools, and plans cost $19 per month for 600 credits, $39 for 1,500, and $79 for 3,500. The full tool reference, permissions, and data handling are on the CalmSEO Google Search Console MCP server page.

Advanced GSC MCP

Advanced GSC MCP is a hosted server from Amin Foroutan, who also maintains the open-source mcp-gsc below. You sign in with Google, and the page says Search Console permissions are requested during that sign-in.

It covers Search Console and GA4 data, and the page says the assistant can inspect pages. The page does not publish a full tool list or the Google scopes it requests.

It lists one-click setup for Claude.ai, ChatGPT, and Claude Desktop, and paste-in setup for Cursor, Windsurf, Zed, and Codex. Plans are $15 per month for up to 3 properties, $40 for up to 10 Search Console and 10 GA4 properties, and $105 for unlimited properties under fair use. A limited free version is also available. Sign-ups open in rounds of 100 seats.

Windsor.ai

Windsor.ai is a marketing data platform with a hosted MCP server. You sign in to Windsor.ai and connect Search Console once.

Its Search Console page lists Search Analytics with extra fields such as branded queries, words in query, and URL path levels, plus read-only sitemap data. Windsor.ai states that its Search Console access is read-only and has no URL inspection.

Documented clients are Claude on the web, Claude Desktop, Claude Code, ChatGPT, Gemini, and Copilot. There is a free plan for one data source. Paid plans start at $19 per month, billed annually, for three sources.

Open-source servers

mcp-gsc by AminForou

mcp-gsc is the most-starred Search Console MCP repository we found on GitHub. It runs locally through uvx mcp-search-console or from a clone, and the README also documents an SSE transport and a Dockerfile for running it on a server. You authenticate with your own OAuth client (Desktop app type) in a Google Cloud project, or with a service account added to your property.

The README lists 20 tools. They cover the property list and site details, search analytics with filters and period comparisons, URL inspection with batches of up to 10 URLs, and sitemap listing, submission, and deletion. Tools that add or delete properties or delete sitemaps stay off unless you set GSC_ALLOW_DESTRUCTIVE=true.

The README has config examples for Claude Desktop, Cursor, and Codex CLI, names Gemini CLI and Antigravity as supported, and mentions a Cursor Marketplace listing. It is MIT licensed and free.

mcp-server-gsc by ahonn

mcp-server-gsc is a Node.js server you run locally with npx -y mcp-server-gsc. It authenticates with a Google service account that you create in Google Cloud and add to your Search Console property. In the source, the Google client requests the webmasters.readonly scope.

The README documents the search_analytics tool in detail, with up to 25,000 rows per request, regex filters, and an option to detect quick wins. The source also defines tools for the site list, URL inspection, and sitemaps.

The README shows a Claude Desktop config and names no other clients. The README and package.json list the MIT license, and it is free.

Suganthan's GSC MCP

Suganthan's GSC MCP (npm package suganthan-gsc-mcp) runs locally. You install it with a setup wizard, npx -y suganthan-gsc-mcp setup, or a one-click .mcpb bundle for Claude Desktop. The README says you still need your own Google OAuth client JSON for now, or a service account. The wizard defaults to a read-only scope, and you can choose full access to use the submission tools.

It has 29 tools. Most are analysis tools built on Search Analytics, such as quick wins, cannibalization checks, content decay, CTR benchmarks, traffic drop diagnosis, and a set of image search tools. It also covers URL inspection, sitemap listing and submission, and Indexing API submission for single URLs and batches.

The setup wizard writes the config for Claude Desktop and Claude Code. It is Apache 2.0 licensed and free.

search-console-mcp by saurabhsharma2u

search-console-mcp puts Google Search Console, Bing Webmaster Tools, GA4, and Google AdSense behind one server. It runs locally with npx or a .mcpb bundle for Claude Desktop. Running npx search-console-mcp setup opens a browser to authorize your Google account, and the installation docs list no Google Cloud project step. A service account is the alternative for servers and automation. The server can hold several Google accounts and picks the right one for each site.

Search Console coverage includes the site list and site management, search analytics, URL inspection, sitemap listing, submission, and deletion, and URL submission through the Google and Bing indexing APIs or IndexNow. It also has SEO audit tools such as quick wins and cannibalization checks. The README says the server is read-only by default and asks for write access the first time a write tool needs it.

The docs have setup steps for Claude Desktop, Cursor, and VS Code, and the README also names Antigravity. It is MIT licensed and free.

Is there an official Google Search Console MCP?

No. Google's list of supported MCP servers (last updated October 26, 2026) does not include Search Console. It covers remote servers for Google Cloud products, Google Workspace apps, and a few others such as Maps and Android Management. Google's MCP repository on GitHub has no Search Console entry. It does link to an official Google Analytics MCP server, a local server labeled experimental.

We also found no Search Console connector from Anthropic or OpenAI. Every Search Console option for Claude and ChatGPT we found, including all seven here, comes from a third party. The open-source servers call Google's Search Console API with credentials you set up. The hosted services connect to Google on your behalf after you sign in.

How to choose

By client

Claude on the web and ChatGPT connect by URL, so start with a hosted server. The mcp-gsc README notes that its local setup works in the Claude Desktop app and does not work on claude.ai. Claude Desktop, Claude Code, Cursor, Codex, and VS Code work with both hosted and local servers.

By setup effort

Hosted servers need a URL and a sign-in. Local servers need Node.js or uv on your machine and an entry in a config file. Three of the four open-source servers also need a Google Cloud project with an OAuth client or a service account. The search-console-mcp docs use a browser sign-in during setup instead.

By permissions

CalmSEO and Windsor.ai are read-only, and mcp-server-gsc requests a read-only scope. Suganthan's GSC MCP and search-console-mcp default to read-only. For write actions, mcp-gsc can submit sitemaps, and Suganthan's GSC MCP and search-console-mcp can submit sitemaps and request indexing once you grant write access.

By features

• URL inspection: mcp-gsc, mcp-server-gsc, Suganthan's GSC MCP, and search-console-mcp. Advanced GSC MCP says it inspects pages.
• Indexing API submission: Suganthan's GSC MCP and search-console-mcp.
• Prebuilt analysis such as quick wins and cannibalization: Suganthan's GSC MCP and search-console-mcp have the most. mcp-server-gsc detects quick wins.
• Other data sources: GA4 in Advanced GSC MCP and search-console-mcp, Bing and AdSense in search-console-mcp, and many marketing sources in Windsor.ai. CalmSEO adds keyword volume, SERPs, ranked keywords, and page audits on the same endpoint.

By cost

The four open-source servers are free. CalmSEO's Search Console tools are free on every plan, and credits apply only to its keyword, SERP, and audit tools. Windsor.ai has a free plan for one data source, and Advanced GSC MCP has a limited free version. Paid plans start at $15 per month for Advanced GSC MCP, $19 for CalmSEO, and $19 for Windsor.ai (billed annually).

When a local open-source server fits

• You want to self-host and keep Google credentials on your own machine or server.
• You want Search Console data to go directly between your machine and Google, with no third-party service in between.
• You need write actions such as sitemap submission or Indexing API requests.
• You want to read or change the code, or add your own tools.
• You are comfortable creating a Google Cloud project and editing MCP config files.

When a hosted server fits

• You use Claude on the web or ChatGPT.
• You do not want to create a Google Cloud project or manage OAuth tokens.
• You want one connection that works the same in several clients.
• Teammates who do not use a terminal need access.

A hosted server passes your Search Console data through the provider's service. Read its privacy policy and the scopes it requests before you connect.

For step-by-step CalmSEO setup, see connecting Google Search Console to Claude and connecting Google Search Console to ChatGPT. The prompts in finding SEO opportunities in Google Search Console work with any connected server that covers search analytics.

Frequently asked questions