A Google Search Console MCP server lets Claude, Cursor or another AI agent read your real clicks, impressions and positions, then answer questions about them in plain English. Google does not ship one, so you either run an open-source server from a Google Cloud project or connect a hosted one on Google’s own consent screen.
Search Console is Google’s own record of how your site does in its results, and most of it goes unread, because every question means date pickers, filters and a CSV export. With a server connected, a question costs one sentence.
- There is no official Google server. Everything is community-built or bundled into an SEO tool.
- Two routes exist. Self-hosted and free but needs Google Cloud, or hosted and instant, like ContextBolt SEO, which connects Search Console on Google’s own consent screen in a couple of clicks and starts with a seven-day trial.
- The Search Console API is free. Google does not charge for read access.
- One step breaks most service-account setups. The account must be added as a user inside Search Console.
- ContextBolt SEO asks for read-only access. AminForou/mcp-gsc can also submit sitemaps.
The best Google Search Console MCP servers, compared
These three come up most often: one hosted, two you run yourself. All three read the same Google API, so the differences are how they sign in, what else they bring, and whether they can change anything.
| Server | Sign-in | What it reads and changes | Cost |
|---|---|---|---|
| ContextBolt SEO (hosted) | Google consent screen | Clicks, positions, quick wins, URL inspection, plus keyword, SERP and backlink data. Read-only scope | Search Console tools spend no credits; seven-day trial |
| AminForou/mcp-gsc (self-hosted) | OAuth client or service account, from a Cloud project | Search analytics, period comparison, URL inspection (10 at a time), sitemaps. Submits sitemaps; delete and property tools off by default | Free, MIT licence |
| ahonn/mcp-server-gsc (self-hosted) | Service account only | Search analytics, up to 25,000 rows a request. Read-only | Free, MIT licence |
Facts from each project’s README and our own code, read 3 Nov 2026.
- Pick ContextBolt SEO if you want Search Console in your agent in a couple of clicks, with keyword difficulty and the live SERP next to your own positions.
- Pick AminForou/mcp-gsc if you want it free and on your own machine, need sitemap tools, and can give Google Cloud fifteen minutes. It reads your side only, with no market data beside it.
- Pick ahonn/mcp-server-gsc if search analytics rows are all you need. It documents one tool and no URL inspection.
How to set up a Google Search Console MCP server
There are two routes. MCP, the Model Context Protocol, is an open standard introduced by Anthropic in late 2024 that lets AI assistants call outside tools through one common interface, and Search Console becomes one more source your assistant can reach.
Route one: self-hosted and open source
AminForou/mcp-gsc is built for SEOs. It covers the performance reports with query, page, country and device breakdowns, period comparisons, URL inspection and sitemaps. Its README recommends signing in with an OAuth client, which reads as your own Google account; a service account is the other option. ahonn/mcp-server-gsc is leaner. It documents one tool, search analytics, and signs in with a service account only. Both are free and MIT-licensed, and both start in Google Cloud, which is where people give up. It’s roughly fifteen minutes of clicking through a console designed for infrastructure engineers rather than SEOs.
- Create a project in Google Cloud Console and enable the Search Console API on it.
- Create credentials: an OAuth client for mcp-gsc’s sign-in-as-you route, or a service account and its JSON key.
- On a service account, add it as a user in Search Console (the next section covers why this matters). OAuth sign-in skips this step.
- Add the server to your MCP client config, pointing at the credentials file.
- Ask “what are my top queries in the last 28 days?”. If real numbers come back, you’re connected.
Route two: hosted
Hosted servers skip the Google Cloud step. You click connect, Google shows its consent screen, and you approve the access it asks for.
ContextBolt SEO is the hosted route we built. Ask it to connect your Search Console, approve read-only scope on Google’s consent screen, and it’s live inside Claude, Cursor or whichever agent you already use. The full walkthrough, including what to ask first, is in connect Google Search Console to AI in one click. For a specific client, SEO inside Claude Code covers it.
The tradeoff on any hosted route is that a third party holds access to your Search Console. So the scope should be read-only, granted on Google’s own screen, and revocable from your Google account permissions page at any time.
Why does my Search Console MCP return empty results?
On a service account, almost always because creating the account doesn’t give it access. It authenticates against Google fine, your MCP client connects fine, nothing errors, and every query comes back empty, because the account can talk to the API but can’t see any of your properties. OAuth sign-in reads as you, so it never hits this.
The fix takes thirty seconds. Open your JSON key and copy the client_email value, which looks like [email protected]. In Search Console, go to Settings, then Users and permissions, click Add user, paste that email, and give it at least Restricted access. Then ask your question again. When a service-account setup returns nothing, check this before you touch the config file.
What can a Search Console MCP server do?
Every server above sits on the same Google API, so they share its edges. The Search Console API has four parts:
- Search Analytics: clicks, impressions, CTR and position, broken down by query, page, country, device and date.
- URL Inspection: whether Google has a page indexed, when it last crawled it, and the reason if it did not index it.
- Sitemaps: list, submit and delete.
- Sites: the properties your account can see, plus add and remove.
None of them presses Request Indexing. The API has no method behind that button. Google’s separate Indexing API is limited to pages with JobPosting or livestream BroadcastEvent markup, so a server that offers to index an ordinary blog post is using it outside Google’s rules. To get a new page found, inspect it, submit the sitemap, and use the button in Search Console yourself.
Two limits shape what you can ask. URL Inspection allows 2,000 calls a day and 600 a minute for each property, per Google’s usage limits, so an agent can check a site’s key pages every day but can’t inspect a large site end to end. And the data runs a couple of days behind: on 3 Nov 2026 the newest day Search Console returned for our own site was 31 Oct.
What to ask once it’s connected
These questions earn the setup time back.
- The striking-distance question: “Which queries am I ranking between position 5 and 20 on, with more than 100 impressions?” Those pages already rank and need a nudge.
- The decay check: “Which pages lost the most clicks in the last 28 days compared to the previous 28?” It catches a problem while it’s still small.
- The zero-click audit: “Which queries have high impressions and under 1% click-through rate?” Some are fixable titles. Some are questions an AI Overview already answers, and no title rewrite will save them. Our free Zero-Click Report runs this one question with a read-only Search Console connection and no setup.
- The measurement question: “Did clicks to this URL improve after the 26th of last month?” If you make changes and never check them, you’re decorating, not doing SEO.
- The mismatch hunt: “Which queries bring impressions to pages that were not written for them?” Google is telling you what it thinks your page is about.
When Search Console emails you about a new reason pages are not being indexed, paste in the example URLs and ask which of them ever earned a click.
The limits of Search Console data
It only goes back 16 months. Year-over-year comparisons work and three-year trends don’t.
Query data is sampled and filtered. Google hides low-volume queries for privacy, so the query rows never quite add up to the totals. That’s Google’s behavior, not a bug in the server.
Position is an average. A query averaging position 8 might be position 3 in the US and 30 elsewhere. Ask for a country breakdown before you act on a blended number.
An assistant can be confidently wrong about strategy even when the numbers are right. It will tell you a page is fine because clicks are up, when clicks are up because of one unrelated query. Treat its SEO advice like its code, and check it before it ships.
For one page’s clicks, queries and index status while you browse, the free Page Insights extension reads the same Search Console data in one click. For the manual route, here is how to see Search Console data for a specific page.
Where does ContextBolt SEO fit?
ContextBolt SEO is our product, so judge this section accordingly.
It includes Search Console access as part of the server, connected through the normal Google consent screen rather than a service account. No Cloud project, no JSON key, no permissions step to forget. It takes a daily Search Console snapshot on its own, so the numbers keep arriving between questions, and every result lands on your SEO Dashboard, so last month’s clicks and positions are still there next month.
The Search Console tools are free and never spend a credit. The credits cover the market data: keyword research, volume and difficulty, SERP overviews, competitor and backlink analysis, page and site audits, and AI visibility. $35 a month for 1,000 credits, and tools cost different amounts. The trial runs seven days with 100 credits to spend.
That’s what lets it do the cross-referencing a standalone Search Console server can’t. Ask which of your striking-distance queries are worth pushing, and it reads your real positions from Search Console and checks the live SERP and the keyword difficulty in the same breath.
The open-source route is still there if you want to own the plumbing. What you give up is the market data beside your own numbers and the SEO Dashboard they save to. The direct comparison covers both sides, and What Is an SEO MCP Server? is the plain-English explainer. For the wider field, Best SEO MCP Servers 2026 compares ten.
Head to head ContextBolt SEO vs Google Search Console MCP Where the free server stops, what the $35 adds beside your own numbers, and how the setup compares. Read the comparison