Google Search Console MCP Server - by k-o.pro (remote)
A Google Search Console Remote MCP server that answers SEO questions instead of returning API rows — across every property in your account. Connect it to Claude by URL and sign in with Google. Nothing to install.
https://gsc.k-o.pro/mcp
Paste that into Claude as a custom connector, sign in with your Google account, and ask "which pages lost the most traffic last month, and why?" — you get a diagnosis: a ranking loss, a CTR collapse, or a demand decline. Not a spreadsheet you still have to read.
Guides on gsc.k-o.pro: claude.ai and Claude Desktop · Claude Code · AI Mode queries · self-hosting
Tool reference by group, with parameters and defaults: opportunities · diagnostics · lookups · image search. Every page there is also served as Markdown (add .md to the address, or send Accept: text/markdown); llms.txt indexes them and llms-full.txt is all of them in one file.
A fork with credit due. The 29-tool foundation and the analysis logic behind it are Suganthan Mohanadasan's work, from Suganthan's GSC MCP. This fork adds multi-property access and remote hosting on top. See Credits.
Contents
Why this one
There are several Google Search Console MCP servers, and a growing number of SEO MCP servers generally. Two things make this one different.
It covers your whole account, not one property. Every property-scoped tool takes a site_url argument, and list_properties discovers what your credential can actually see. One install answers questions about all your sites — you never edit a config file and restart to look at a different one. (This is what upstream issue #9 asked for.)
It runs as a remote MCP server, with per-user Google sign-in. Most MCP servers are local-only: one process, on one laptop, with one credential — which is why they cannot be shared, and why the claude.ai and Claude Desktop connector UIs cannot add them at all. This one runs as a hosted service over Streamable HTTP at gsc.k-o.pro: add it as an MCP connector by URL, sign in with your own Google account, and Google's own Search Console permissions decide what you see. Ten people share one deployment and each sees only their own properties — nobody copies a credential anywhere.
It is a full MCP OAuth authorization server: dynamic client registration, PKCE, rotating tokens, and a consent screen of its own. That is what lets the claude.ai and Claude Desktop connector UIs onboard it from nothing but a URL.
Also: it returns SEO analysis rather than rows, every answer states which property it came from, and it exposes Google's type=image surface that most third-party tools skip entirely.
It is built for the people who live in Search Console — in-house SEOs, consultants, and agencies running many client properties from one place.
What you can ask
"What keywords am I almost ranking for?"
"Which pages lost the most traffic in the last month, and why?"
"Do I have any pages cannibalising each other?"
"Compare quick wins across all my properties."
"Which pages get image impressions but no clicks?"
"Is this URL indexed, and if not, why not?"
"Check that 40% CTR figure before I put it in the deck."
Answers carry _meta provenance naming the source, the exact parameters, and the property used — so an answer is never ambiguous about which site it describes. position is labelled as the impression-weighted average it actually is, not a rank-tracker position.
Get connected
The server is hosted at https://gsc.k-o.pro/mcp. There is nothing to download, no API key to generate, and no config file to edit.
claude.ai and Claude Desktop
Add to Claude opens claude.ai with the connector pre-filled; you confirm the address before anything connects.
Or by hand: Settings → Connectors → Add custom connector, then paste:
https://gsc.k-o.pro/mcp
Claude Code
claude mcp add --transport http gsc https://gsc.k-o.pro/mcp
What happens next
Your browser opens and you will see two screens, in this order:
以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗
