- Overview
- How it compares
How it compares
What to ask of any Search Console MCP server before you connect it to your account, and the answers for this one.
The questions worth asking
Ask these of any Search Console MCP server. Other servers are not named here: their specifications change, and a table about them would be stale or unverified. These are the answers for this one.
| Question | This server |
|---|---|
| Do you need a Google Cloud project? | No, for the hosted instance. Self-hosting needs your own OAuth client. |
| Does it work in claude.ai and Claude Desktop, or only locally? | Both. It is a remote server over Streamable HTTP with its own OAuth, so connector UIs add it by URL; the same code runs locally over stdio. |
| One property per config, or all of them? | Every property your Google account can see, from one connection. |
| What can it change in your Google account? | Nothing, on the hosted instance: its only Search Console permission is webmasters.readonly, which is read-only. Signing in also uses Google's basic openid and email scopes, only to identify you. |
| Is your Search Console data stored? | No. It is fetched live for each question and passed back to your client. |
| What do the tools return? | Diagnoses with provenance: every answer names the property, the parameters and the date range. 32 tools; 30 run on the hosted instance. |
| Does it show results visually? | Ten tools render cards and sortable tables in clients that support MCP Apps; every client gets the same data as text. See all tools. |
| Does it cover Google Images? | Yes, eight tools on the type=image search type, including an on-page image audit. |
| Can it find AI Mode and AI Overview queries? | It finds queries shaped like AI conversations and sorts them into seven buckets. See AI Mode queries. |
| Price and licence | The hosted instance is free. The code is Apache 2.0 and public on GitHub. |
Why a remote server
Most MCP servers are local-only: one process, on one laptop, holding one credential. That is why they cannot be shared, and why the claude.ai and Claude Desktop connector interfaces cannot add them at all.
This one runs as a hosted service over Streamable HTTP and implements the MCP authorization spec: dynamic client registration, PKCE, rotating tokens, and a consent screen of its own. That is what lets a connector interface add it from nothing but a URL. It also means a team shares one deployment while each person signs in as themselves and sees only their own properties. Nobody copies a credential anywhere.
Hosted, or your own
Hosted at gsc.k-o.pro | Your own copy | |
|---|---|---|
| Setup | Add a URL, sign in with Google | Clone, build, bring a Google OAuth client |
| Where the Google token lives | On this server, encrypted | On your machine or your server |
| Access to Google | Read-only | Read-only, or full if you choose |
| Indexing tools | Not available | Available with full access |
The self-hosting guide covers the second column.
About this page
Version 3.11.0 · page updated 10 November 2026 · changelog