Google Search Console MCP server
officialGoogle does not publish an MCP server for Search Console, so Walma built one: gsc-mcp, open source and read-only, signing in with a service account. The team asks about clicks, impressions, sitemaps and indexing straight from its AI assistant.
What an agent can do
- → Pull clicks, impressions, CTR and position
- → Filter by query, page, country and device
- → Compare periods and spot quick wins
- → Inspect indexing status for a URL
- → List submitted sitemaps
The service account has to be added as a user on each Search Console property, and the data lags about two days behind.
About the Google Search Console MCP server
gsc-mcp is a small open source MCP server for Google Search Console, built by Walma and released under the MIT licence. It is available as the npm package @walma-labs/gsc-mcp and on GitHub. Walma uses it daily for its own SEO work. The server runs on your side, on a computer or centrally in a container, and fetches search data through Google's own Search Console API.
SEO and content teams use it to ask which queries bring the most clicks to a given page, which pages lost the most between two periods, and which queries with many impressions sit at positions 11 to 20. It also lists submitted sitemaps with their errors and indexed counts, and checks whether a single URL is indexed and which canonical address Google has chosen.
The server is entirely read-only and cannot change anything in Search Console. It signs in with a service account instead of a personal Google login, so the key can be rotated and revoked. The service account only sees the properties where you have added it as a user. The key file does grant read access to all your search data, so for a whole team it should be held centrally and not on individual laptops.
Things to ask
- Which queries bring the most clicks to the pricing page, and what is our average position for each?
- Compare the last 28 days with the 28 days before. Which pages lost the most clicks?
- List queries with more than 500 impressions where we rank between 11 and 20.
- Is the new guide indexed, and which address does Google consider canonical?
- List our sitemaps and show which ones have errors.
Tools the server exposes
- list_sites
- search_analytics
- compare_periods
- list_sitemaps
- inspect_url
Part of these packages
Google Search Console is part of these Walma packages.
Questions about Google Search Console MCP
Does Google have an official MCP server for Search Console?+
Google does not publish an MCP server of its own for Search Console. That is why Walma built gsc-mcp as open source under the MIT licence. It is unofficial, meaning neither made nor endorsed by Google, but it uses Google's official Search Console API and only asks for read access.
Is gsc-mcp free?+
Yes, the server itself is open source under the MIT licence and costs nothing. You need a Google Cloud project with the Google Search Console API enabled, a service account with a JSON key, and Node 20 or newer. The service account needs no roles in the Cloud project.
Where is the server, and does it have a URL?+
There is no shared address. The server is the npm package @walma-labs/gsc-mcp, with the source at github.com/Walma-Labs/gsc-mcp, and it is started locally with npx. The package also ships an HTTP entrypoint and a Dockerfile if you want to host it centrally. The HTTP variant has no sign-in of its own, so it belongs behind a gateway or reverse proxy.
How does sign-in work?+
With a service account from Google Cloud. You create a JSON key and add the service account's email address as a user on each property in Search Console. Full permission is enough for search analytics, comparisons and sitemaps. URL inspection needs Owner or Full depending on the property type. No personal Google login is needed on the machine that runs the agent.
Is it read-only?+
Yes, entirely. All five tools read, and the server only asks for the webmasters.readonly scope. It cannot submit sitemaps, request indexing, remove URLs or change users. Those things still happen in Search Console.
Which AI assistants does it work with?+
The README shows the configuration for Claude Code, Claude Desktop and Cursor, and the server works with other MCP clients that can start a local server. In the desktop clients the path to the key file has to be absolute, because they do not expand the ~ character or inherit the shell's PATH.
Why do the numbers not match what I see in Search Console?+
For two reasons. Search analytics data lags about two days, so the server defaults to a date range that ends two days ago. Google also anonymises rare queries, which means totals by query will not equal totals by page. Ask the assistant to take totals per page or for the whole site.
Missing a connection?
We build and review MCP servers for teams that need them, and run them behind the same policy and log as the rest of the gateway.