Google Search Console MCP servers compared
There are three ways to put Search Console inside Claude or ChatGPT: a hosted server that is free, a hosted server that charges once you pass its cap, or an open-source server you run yourself. The trade is always the same one, between what you set up and what you give up.
We build one of the options below, so read this with that in mind. Every claim about another product is taken from that product's own pages on October 19, 2026 and linked, so you can check it rather than take our word. Prices change; the date is there for a reason.
The short answer
If you want the widest Search Console coverage at no cost, GSC PAP is free, exposes 36 read-only tools, and is the only option here that keeps your history growing past Google's 16-month window. If you want your assistant to submit sitemaps as well as read data, MCP Search Console has opt-in write tools. If you need Search Console next to 350 other marketing sources for BI work, Windsor.ai is a connector platform rather than an SEO server. If everything has to run on your own infrastructure, self-host and accept the Google Cloud setup.
Side by side
| Option | Tools | Data sources | Cloud project | Past 16 months | Write actions | Price |
|---|---|---|---|---|---|---|
| GSC PAP Hosted, free | 36 | Search Console, GA4, PageSpeed, live Google SERPs | No | Yes. The archive keeps every day after you connect | None. Read-only scopes | $0 |
| MCP Search Console Hosted, free tier then paid | 16 | Search Console, PageSpeed, plus DNS, robots, redirect and TLS checks | No | Not advertised | Sitemap submit and delete, opt-in | Free for 15 pulls a day, 40 a month and 3 properties. Solo 4.99 EUR a month, Team 29.99 EUR |
| OpenSEO Hosted paid, or self-host | 2 | Search Console | No for hosted, yes to self-host | No. 16-month lookback, same as the Search Console interface | None | $10 a month hosted. Self-hosting is free and open source |
| GrowthSpree Hosted, free to start | Not stated. Ships 20 ready-made prompts | Search Console, GA4, Google Ads, LinkedIn and Meta Ads, HubSpot, Microsoft Ads | No | No. Up to 16 months | Not stated | Free to start, Premium adds more sources |
| Windsor.ai Connector platform with an MCP server | Not applicable. It is a connector | Search Console, GA4, Google Ads and 350+ others | No | Not advertised | Not applicable | Free forever for one source, then from $19 a month |
| Self-hosted open source You run it | Varies, typically 15 to 25 | Search Console, whatever the project adds | Yes. Your own project, OAuth client and credentials file | Only if you build the storage yourself | Depends on the project | No licence cost. You pay in setup and upkeep |
Checked October 19, 2026. Tool counts are what each product publishes about itself.
What to check before you pick one
- Does it need a Google Cloud project?
- This is the step that stops most people. Self-hosting means creating a Cloud project, enabling the Search Console API, creating an OAuth client, downloading a credentials file and keeping the refresh token alive. Every hosted option on this page removes it, because the vendor registered one OAuth client for everybody.
- Can it read past Google's 16 months?
- Search Console drops data older than about 16 months, permanently, and nothing can recover a day you never stored. The only fix is a server that copies your history on the day you connect and keeps appending. Check whether the option you are looking at stores anything at all, or just proxies Google's window.
- Is it read-only?
- Some servers can submit or delete sitemaps. That is useful and also a sharp edge: an assistant that can delete a sitemap will eventually be asked to. If you would rather that class of mistake be impossible, pick a server whose Google scopes are read-only, and check the scope, not the marketing.
- How many tools, and are they the ones you will use?
- A high count means nothing on its own. What matters is whether the questions you actually ask map to one call: decaying pages, cannibalization, quick wins, bulk URL inspection, a period diff. Two tools can answer anything in theory, if you are willing to assemble it by hand every time.
- Does it reach beyond Search Console?
- Search Console stops at the click. If you want to know which organic landing pages convert, the server has to read GA4 as well, and join the two by page. If you want to know why a good position gets a bad CTR, it has to see the live SERP above you.
- Per-site control and an audit log
- Google's webmasters.readonly scope is account-wide: it covers every property you can see, with no per-site granularity. A server worth trusting adds its own allowlist on top, lets you scope a token to a subset of sites, and shows you every call that was made.
- What the free tier actually limits
- Free usually means a cap on data pulls per day or per month, or on how many properties you can connect. Those caps are reached quickly, because one question from an assistant is several calls. Read the cap, not the word.
- Which clients it supports
- A server reachable over HTTP with OAuth works as a one-click connector in Claude.ai and ChatGPT. A server that only runs locally over stdio needs a config file on every machine, and a bridge process for browser clients.
The one difference that cannot be undone later
Every other row in that table can be changed by switching products. History cannot. Search Console keeps roughly 16 months and then deletes, so the day you start storing is the earliest day you will ever be able to ask about. A server that proxies Google gives you the same 16 months next year that it gives you today. A server that archives gives you 16 months today and 28 months a year from now.
That is why starting the archive is worth doing even if you are still deciding. The cost of connecting and changing your mind is nothing. The cost of deciding in six months is six months of history you cannot buy back.
Where GSC PAP is the wrong answer
If you want your assistant to act on Search Console rather than read it, submitting a sitemap or requesting indexing, our scopes make that impossible by design. Pick a server with write tools.
If your data cannot leave your own infrastructure, no hosted service qualifies, ours included. Self-host and budget the setup.
If Search Console is one of fifteen marketing sources you are pulling into a warehouse, a connector platform is the right shape of tool and we are not one.
And if you need a guarantee of what this costs in two years, we are in a free public preview with paid plans coming at v1.0. The terms are written down on the pricing page, including the 60 days notice, but a preview is a preview.
Questions people ask before choosing
- What is the best Google Search Console MCP server?
- It depends on which constraint binds. For the most Search Console coverage at no cost, including GA4, PageSpeed and history past Google's 16-month window, GSC PAP is free and exposes 36 read-only tools. If you want your assistant to submit sitemaps as well as read data, MCP Search Console has opt-in write tools. If you need Search Console alongside 350 other marketing sources for BI, Windsor.ai is a connector platform rather than an SEO server. If everything must run on your own infrastructure, self-host an open-source server and accept the Google Cloud setup.
- Is there a free Google Search Console MCP server?
- Yes. GSC PAP is free with no daily or monthly pull cap, no property limit and no credit card. GrowthSpree is free to start. MCP Search Console has a free tier capped at 15 data pulls a day, 40 a month and 3 properties. Self-hosted open-source servers have no licence cost, but need your own Google Cloud project.
- Do I need a Google Cloud project for a Search Console MCP server?
- Only if you self-host. Every hosted server on this page registered its own OAuth client, so you sign in with Google and nothing else. Self-hosting means creating the project, enabling the API, creating OAuth credentials and keeping the refresh token working, which takes most people around 45 minutes before the first query.
- Can an MCP server read Search Console data older than 16 months?
- Only if it stored it. Google deletes Search Console performance data older than about 16 months and no API can bring it back. A server that keeps its own archive, like GSC PAP, copies the 16 months Google still has on the day you connect and then stores every new day, so the usable history grows past the limit from that day forward.
Try the free one first
Sign in with Google, pick your properties, and ask your assistant a question. It costs nothing, it takes about a minute, and it starts your archive on today's date rather than the date you finish deciding.