Connect Google Search Console to Claude

Add this server to claude.ai or Claude Desktop as a custom connector. It takes one URL and a Google sign-in, and gives Claude read-only access to every Search Console property your account can see.

What you need

A Google account with access to at least one Search Console property, and claude.ai or Claude Desktop. No Google Cloud project, API key or download.

Add the connector

With one click

This opens claude.ai's Add custom connector dialog with the name and URL already filled in. claude.ai asks you to confirm the address before anything connects.

Add to Claude

By hand

In claude.ai or Claude Desktop, open Settings → Connectors → Add custom connector, give it a name such as Google Search Console, and paste:

https://gsc.k-o.pro/mcp

Both /mcp and /mcp/ work.

Sign in

Your browser opens two screens, in this order:

This server's own consent page. It names the application that asked and the exact address the result will be sent to. It exists so a connection request you did not start can be refused; cancel if anything looks wrong.
Google's sign-in. It asks for read-only Search Console access (webmasters.readonly) and your email address, and nothing else.

Check that it works

Ask Claude: “List my Search Console properties.” You get every property your Google account can see, with its type and your permission level. From there, name a property in any question:

“What am I almost ranking for on sc-domain:example.com?” — opportunity tools
“Which pages lost the most traffic last month, and why?” — diagnostic tools
“Is https://example.com/page indexed?” — lookups
“Which of my queries look like AI Mode conversations?” — AI Mode queries

Tired of naming the property every time? Ask Claude to run set_default_property.

Troubleshooting

What you see	Why, and what to do
`access_denied` from Google	While Google's app verification is pending, Google limits sign-in to an approved list of accounts. Open an issue to ask for access, or run your own copy.
The connector dialog rejects the URL	Check it is exactly `https://gsc.k-o.pro/mcp`.
“This session belongs to a different user”	A stale connector entry. Remove it and add it again.
A tool says a property is not available	Google's own permissions apply. Check that the account you signed in with can see the property in Search Console itself.
`GSC_SITE_URL environment variable is required`	A tool ran without a property and you have no default. Name one, or run set_default_property.
`429` or `503` with `Retry-After`	A capacity limit. Wait the stated interval and ask again.

Disconnecting

Either of these is enough:

Ask Claude to run disconnect_account. It erases the stored Google connection, every token and your saved settings, and ends your sessions.
Remove the app at myaccount.google.com/permissions. The stored credential stops working and the server erases it the next time it tries to use it.

Removing the connector in Claude only removes it from Claude. Details are in the privacy policy.

About this page

Built and run by Oleksii Khoroshun, an SEO with nine years in the field who builds tools at k-o.pro. It is a fork of Suganthan's GSC MCP by Suganthan Mohanadasan: the analysis logic and most of the tool set are his design, and this fork adds multi-property access, the remote server and per-user sign-in.

Version 3.8.0 · page updated 13 October 2026 · changelog