Which Search Console MCP server should you use?
The best Google Search Console MCP server depends on who sets it up. If you are happy to create a Google Cloud project and an OAuth client, the open-source AminForou/mcp-gsc is the most-starred free option (about 2,060 GitHub stars as of October 2026), and Suganthan’s GSC MCP has the deepest built-in analysis. If you want Search Console and Bing Webmaster Tools inside Claude or ChatGPT on the web, with no Google Cloud setup, use a hosted server that signs you in with OAuth.
A note on bias: this is the GSC MCP Server blog, and our hosted server is one of the options below. We have kept the comparison factual. Every competitor detail comes from its own README or pricing page, checked on 29 October 2026, and we say plainly where another option is the better pick.
| If you are… | Start with | Why |
|---|---|---|
| A developer with a few sites who wants no third party in the data path | mcp-gsc or Suganthan’s GSC MCP | Free, local, data goes from your machine straight to Google |
| Running scheduled jobs on a server or in CI | ahonn/mcp-server-gsc or mcp-gsc with a service account | No browser sign-in; access is granted per property |
| Technical, and want Google, Bing, GA4 and AdSense locally | saurabhsharma2u/search-console-mcp | Broadest local coverage, optional write actions |
| A marketer or founder using Claude or ChatGPT in the browser | A hosted server | Web clients need a remote server; no Cloud project or runtime to install |
| An agency with many client properties on Google and Bing | A hosted multi-account plan | One sign-in per account, nothing to maintain on each laptop |
New to the idea? Start with what a Search Console MCP server is and come back for the shortlist.
What to compare before you install one
Every server on this list calls the same public Search Console API, so the raw numbers are identical. The differences are in setup, scope and maintenance.
- Where it runs. A local server is launched by your desktop app over stdio. A remote server lives at an HTTPS URL. Claude on the web and ChatGPT on the web can only add remote servers; the mcp-gsc README notes that its standard setup works in the Claude Desktop app, not the claude.ai website.
- How it gets Google access. Three patterns: your own OAuth client (a Desktop app credential from a Google Cloud project), a service account you add as a user on each property, or a hosted OAuth sign-in. The MCP authorization spec bases remote servers on OAuth 2.1 and tells stdio servers to read credentials from the environment instead, which is why local servers ask you for key files.
- Read-only or write. Google offers a read-only scope,
webmasters.readonly. Servers that submit or delete sitemaps, or add and remove properties, need the full scope. Read-only means a confused prompt cannot change anything. - Bing coverage. Most servers are Google-only.
- URL Inspection. Whether you can check index status, last crawl and canonicals, and whether it batches several URLs.
- Multiple accounts. Agencies often have properties spread across several Google logins.
- Maintenance. Someone has to keep up with SDK and API changes. When version 2.0 of the
mcpPython SDK shipped on 28 July 2026, it removed a module that mcp-gsc relied on, and fresh installs crashed until the project pinned the older SDK in version 0.3.3. That is normal open-source life, but it lands on you. - Data path and price. With a local server, your data goes from your machine to Google. With a hosted one, the vendor stores your tokens and the data passes through its servers.
Open-source Search Console MCP servers on GitHub
All four of the main open-source servers are free and permissively licensed. Star counts and last-commit dates are from GitHub on 29 October 2026, and every one of them had commits in the last two months.
AminForou/mcp-gsc (Python)
mcp-gsc has about 2,060 stars and a last commit on 15 September 2026 (version 0.4.1). It runs through uvx from the PyPI package mcp-search-console and offers around 20 tools: search analytics with filters, period comparisons, URL inspection including batches of up to 10 URLs, and sitemap listing and submission. Deleting sitemaps and adding or removing properties stay switched off unless you set GSC_ALLOW_DESTRUCTIVE. You need a Google Cloud project with the Search Console API enabled, then either an OAuth client or a service account. It is Google-only, has the most detailed setup documentation of the group (including video walkthroughs), and its author also sells a hosted version, covered below.
Suganthan’s GSC MCP (Node)
Suganthan’s GSC MCP has about 167 stars and a last commit on 27 September 2026. Its 29 tools lean towards analysis rather than raw rows: quick wins, content decay, cannibalisation, traffic-drop diagnosis, an image-search suite, and a verify_claim tool that re-queries Search Console to check a number before Claude presents it. A setup wizard (npx -y suganthan-gsc-mcp setup) writes the client config for you, but the README says you still need your own Google OAuth client JSON once. The wizard defaults to read-only; choosing full access enables Indexing API and sitemap submission tools. It is Google-only and runs entirely on your machine.
saurabhsharma2u/search-console-mcp (Node)
search-console-mcp has about 313 stars and the most recent commit of the group (21 October 2026). It covers Google Search Console, Bing Webmaster Tools, GA4 and AdSense. npx search-console-mcp setup opens a browser to authorise Google; Bing uses a Bing Webmaster API key and GA4 a service account. It has write tools for sitemaps, property management and URL submission (including IndexNow), and since version 2.1.4 those need an explicit write authorisation, so setup stays read-only by default. It also resolves which of several accounts owns a site automatically.
ahonn/mcp-server-gsc (Node)
mcp-server-gsc has about 282 stars and a last commit on 4 September 2026. It needs Node.js 18 or later and a service account key passed through GOOGLE_APPLICATION_CREDENTIALS, with the service account’s email added to each property. Its eight tools cover site listing, search analytics of up to 25,000 rows per request with regex filters, quick-win detection, URL inspection and sitemaps, including submission. No browser sign-in makes it a good fit for automation.
Others worth knowing
mikusnuz/gsc-mcp(about 8 stars) wraps every Search Console API endpoint plus the Indexing API.- Bing-only servers:
isiahw1/mcp-server-bing-webmaster(about 31 stars, last commit February 2026) andzizzfizzix/mcp-server-bwt(about 7 stars, last commit September 2026). Both take a Bing Webmaster API key.
What local setup actually involves
- In Google Cloud Console, create a project and enable the Search Console API.
- Configure the OAuth consent screen, create an OAuth client ID of type Desktop app, and download the client secrets JSON. For a service account, create a JSON key instead and add the account’s email under Search Console → Settings → Users and permissions on every property.
- Install the runtime:
uvfor Python servers or Node.js for the others. - Add the server to your client’s config file. GUI apps often need the absolute path to
uvxornpxand to the JSON file. - Fully quit and reopen the client, then complete the browser sign-in on first use.
It is a one-off job, but it is the step where most non-developers get stuck, and you repeat it on every machine.
Hosted Search Console MCP servers
A hosted server runs on the vendor’s infrastructure. You paste one URL into your AI client and sign in with OAuth. The trade-off is trust: the vendor holds your tokens, and your data passes through its servers. Prices below are as listed on 29 October 2026.
GSC MCP Server (ours)
GSC MCP Server, our hosted Google Search Console MCP server, reads Google Search Console and Bing Webmaster Tools, both connected through OAuth sign-in, with no Google Cloud project or API key. It requests Google’s read-only webmasters.readonly scope and Bing’s read scope, stores tokens encrypted, and exposes 12 read-only tools, including query_search_analytics, find_keyword_cannibalization, inspect_url, get_bing_crawl_stats and multicall. It works with Claude (web, desktop and Claude Code), ChatGPT, Cursor, VS Code, Codex and other MCP clients.
Plans: Free (one Google or Bing account, 30 tool calls a month, every tool), Pro at $9 a month (5 accounts, 10,000 calls) and Agency at $29 a month (20 accounts, 50,000 calls).
Where it falls short: it cannot submit sitemaps or request indexing, it has no GA4 data, the Free plan’s 30 calls are enough to evaluate it but not to run weekly reports, and the self-hosted release is not available yet.
Advanced GSC MCP
The hosted version from mcp-gsc’s author, Advanced GSC MCP, uses Google sign-in with no separate OAuth step. Search Console is on every plan and GA4 on Pro and Max, plus Google and Bing SERP lookups, keyword research and Core Web Vitals, with backlink analysis on Max. Starter is $15 a month for up to 3 properties, Pro $40 and Max $105. There is a limited free version, and paid seats are released in rounds of 100. The page does not say it reads Bing Webmaster Tools data.
Search Console MCP (mcpsearchconsole.com)
Search Console MCP is Google-only and read-only by default (webmasters.readonly), with sitemap submission and deletion as opt-in write actions. Its 16 tools add site checks such as DNS, TLS, redirects, robots.txt and page speed, plus shared notes. The free tier allows 15 data pulls a day and 40 a month on 3 properties; Solo is €4.99 a month and Team €29.99. It is the cheapest unlimited Google-only option we found.
Data-connector platforms
Windsor.ai hosts one MCP across its data connectors. Its Search Console connector is read-only and returns search analytics with some extra derived fields, but has no URL inspection or sitemap tools. The free plan covers one data source; paid plans start at $19 a month billed annually. It suits teams that already blend Search Console with GA4 and ad data there. Ekamoira also bundles a hosted Search Console MCP with its platform plans after a 30-day trial, according to its own comparison page.
Google Search Console MCP servers compared
The side-by-side view, as of 29 October 2026. “Changes GSC” means the server can modify something in Search Console, such as submitting a sitemap.
| Server | Runs | Google access | Bing | URL Inspection | Changes GSC | Price |
|---|---|---|---|---|---|---|
| mcp-gsc | Local (Python) | Own OAuth client or service account | No | Yes, batches of 10 | Sitemap submit; deletes off by default | Free |
| Suganthan’s GSC MCP | Local (Node) | Own OAuth client or service account | No | Yes | Only with full scope | Free |
| search-console-mcp | Local (Node) | Browser sign-in wizard or service account | Yes (API key) | Yes | Only after explicit write consent | Free |
| mcp-server-gsc | Local (Node) | Service account | No | Yes | Sitemap submit | Free |
| GSC MCP Server | Hosted | OAuth sign-in, read-only | Yes (OAuth) | Yes | No, read-only | Free (30 calls), $9, $29 |
| Advanced GSC MCP | Hosted | Google sign-in | SERP lookups only | Yes | Not stated | Limited free, $15–$105 |
| Search Console MCP | Hosted | OAuth sign-in, read-only | No | Yes | Opt-in sitemap submit and delete | Free (40 pulls), €4.99, €29.99 |
| Windsor.ai | Hosted | Windsor account connection | Not on its GSC page | No | No, read-only | Free (1 source), from $19 |
Which servers also cover Bing Webmaster Tools?
Most Search Console MCP servers ignore Bing, which leaves a gap. Microsoft documents that Copilot sends generated search queries to the Bing search service to ground its answers, and Bing has been reported as one of ChatGPT search’s providers. Bing data also comes from a different audience, so it catches problems Google data hides. We cover the details in why Bing Webmaster Tools matters for AI search.
- GSC MCP Server connects Bing through OAuth, so there is no key to copy. Every shared tool accepts
provider: "all"to return Google and Bing side by side,list_sitemapsincludes feeds submitted to Bing, andget_bing_crawl_statsreports daily pages crawled, crawl errors, pages in the index and inbound links. - saurabhsharma2u/search-console-mcp reads Bing with an API key and adds a Google-versus-Bing comparison tool.
- Bing-only servers (isiahw1, zizzfizzix) pair with any Google-only server. Both include URL submission.
If you use an API key, remember Microsoft’s rules: according to its Bing Webmaster API access guide, only one key can be generated per user and it works for all of that user’s verified sites. Treat it like a password, and if it leaks, delete it and generate a new one.
One gap no server can close: Bing’s AI Performance report (citations in Copilot and Bing’s AI summaries) has no documented API, so it stays in the Bing Webmaster Tools interface.
Security checklist for any GSC MCP server
- Grant read-only access unless you have a concrete reason to write. The Google consent screen should ask only to view Search Console data.
- Keep write tools off. An agent can call a tool you did not expect, especially in long sessions. Deleting a sitemap is the obvious accident to avoid.
- Scope service accounts tightly. Add them only to the properties they need, with the lowest permission that still works, and remove them under Settings → Users and permissions when you are done.
- Know where tokens live. Local servers cache them on your machine (search-console-mcp uses the OS keychain). Hosted servers store them on the vendor’s side, so check that the vendor says how; ours are encrypted, and Search Console MCP states AES-256-GCM.
- Pin versions of local servers. A config that runs
@lateston every launch pulls new code silently. - Mind what you combine. An assistant that can read your private data, read untrusted web pages and send data out is the risky mix. Keep your SEO data connector away from tools that do all three.
- Revoke cleanly. Remove the app from your Google Account’s third-party connections, delete unused service account keys, and regenerate a leaked Bing key.
Limits every server shares
Because every server uses the same APIs, these limits apply whichever one you choose. Our guide to Search Console API row limits and quotas covers them in depth.
| Limit | Value |
|---|---|
| Rows per Search Analytics request | 1–25,000 (default 1,000); Google returns top rows and doesn’t guarantee all of them |
| History | 16 months |
| Freshness | Usually 2–3 days for final data |
| Search Analytics quota | 1,200 queries per minute per site and per user |
| URL Inspection quota | 2,000 a day and 600 a minute per property |
| Request indexing | Not in the Search Console API |
| Generative AI performance report | Not documented in the API, so no MCP server can read it |
Sources: Search Analytics API reference and Search Console API usage limits. Some servers expose Google’s Indexing API as a “submit URL” tool, but Google officially limits that API to pages with JobPosting or BroadcastEvent markup.
Your AI client adds its own ceiling. Claude Code warns when a tool returns more than 10,000 tokens and cuts output at 25,000 by default, so ask for 50–200 rows rather than everything. GSC MCP Server caps limit at 1,000 rows per call and pages further with startRow. If you check many URLs after a launch, our guide to URL inspection from Cursor and VS Code shows how to stay inside the daily quota.
Test-drive any server with five questions
Before you commit, ask each candidate the same five questions about a property you know well, then check the answers against the Search Console interface.
- Which properties can you see?
- How did the last 28 days compare with the previous 28, on Google and Bing?
- Which queries sit in positions 8–20 with real impressions?
- Are any of those queries split across two of my pages?
- Is my most important page indexed, and did Google pick my canonical?
On GSC MCP Server those map to list_search_properties, compare_search_periods, get_search_opportunities with strategy: "striking_distance", find_keyword_cannibalization and inspect_url. On other servers, the tool names differ but the questions work the same.
List every Search Console and Bing property you can access. Then, for example.com, compare the last 28 days with the previous 28 days on Google and Bing separately: clicks, impressions, CTR and average position, with the change for each.
Find striking distance queries for example.com over the last 90 days (average position 8–20, at least 100 impressions). Then check whether any of those queries are split across two or more of my pages, and show each page’s share of impressions.
Inspect https://example.com/pricing/ and tell me the index verdict, the coverage state, the last crawl date, and whether Google’s chosen canonical matches the canonical I declared.
Then test efficiency. Batching saves round trips and context, though on metered plans, ours included, each call inside a batch still counts:
In one multicall, get the 28-day overview, the top 20 queries, the top 20 pages and the sitemap status for example.com. Then write a five-bullet summary of what changed and what needs attention.
Score each server on four things: did it pick the right property, do the totals match the interface (small differences from rounding and fresh data are normal), how many tool calls did it use, and was the output small enough to read. Setup steps for each client are in how to connect Search Console to Claude, ChatGPT and Cursor, and terminal users can follow Claude Code for SEO.
Verdict: the best server for each use case
When a local open-source server makes sense
Choose one if you are comfortable in Google Cloud Console and a terminal, work in a desktop client, want no vendor between you and Google, and accept fixing it yourself when something breaks.
Pick mcp-gsc for the most-starred, best-documented option, Suganthan’s GSC MCP for built-in analysis and image search, search-console-mcp if you also want Bing, GA4 or AdSense, and mcp-server-gsc for service-account automation.
When a hosted server makes sense
Choose one if you use Claude or ChatGPT in the browser, you or your clients are not developers, you manage several Google or Bing accounts, or you would rather not maintain anything.
Pick GSC MCP Server for Google and Bing together with read-only access, Search Console MCP for the cheapest Google-only plan with optional sitemap submission, and Advanced GSC MCP if you want GA4 and some third-party SEO data in the same connector.
When ours is not the right pick
If you need sitemap submission or IndexNow pings, want GA4 in the same place, or must keep every byte on your own machine, choose one of the alternatives above, or one of the marketing MCP servers for GA4, ads and CRM. Our server is deliberately read-only, and the self-hosted release is not out yet. If you also need competitor keywords or backlinks, that is a different category of tool; we compare them in Search Console MCP vs Ahrefs and Semrush MCP.
If a read-only Google and Bing connector fits, the Free plan is enough to run the five test questions above on your own site.
Frequently asked questions
Is there an official Google Search Console MCP server?
We’re not aware of one as of October 2026. Google publishes an official, experimental Google Analytics MCP server, but every Search Console MCP server we know of, including ours, is third-party code that calls the public Search Console API. They all return the same underlying data and share the same API limits.
Is there a free Search Console MCP server?
Yes. The open-source servers (mcp-gsc, Suganthan’s GSC MCP, saurabhsharma2u/search-console-mcp and ahonn/mcp-server-gsc) are free; you pay in setup time and maintenance. Several hosted servers have free tiers: GSC MCP Server’s Free plan covers one Google or Bing account and 30 tool calls a month, and Search Console MCP’s free tier allows 40 data pulls a month.
Do I need a Google Cloud project to use a GSC MCP server?
For most local servers, yes: you create a project, enable the Search Console API, and make either an OAuth client or a service account. Hosted servers handle that for you, so you only sign in with Google. saurabhsharma2u/search-console-mcp is a local exception that offers a browser sign-in wizard.
Which Search Console MCP servers also support Bing Webmaster Tools?
As of October 2026, GSC MCP Server (hosted, Bing via OAuth) and saurabhsharma2u/search-console-mcp (local, Bing via API key) cover both Google and Bing. Bing-only servers such as isiahw1/mcp-server-bing-webmaster and zizzfizzix/mcp-server-bwt can sit alongside a Google-only server.
Can an MCP server submit sitemaps or request indexing?
Some can submit or delete sitemaps through the Search Console Sitemaps API. None can press Search Console’s Request indexing button, because the API has no such method; Google’s separate Indexing API is officially limited to JobPosting and BroadcastEvent pages. GSC MCP Server is read-only and changes nothing.
Is it safe to give an AI assistant access to Search Console?
It is reasonably safe if you grant read-only access, keep write tools switched off, know where your tokens are stored, and avoid combining the server with tools that read untrusted web pages and can send data out. Revoke access from your Google Account’s third-party connections when you stop using a server.