mcpbeat Sign in

Google Search Console MCP Server

answering

Google Search Console MCP is answering right now. Last checked 7 min ago.

Google Search Console SEO analytics, keyword rankings, URL inspection, sitemaps, PageSpeed checks.

Uptime history 91 days of history · worst day 99%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
201 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Google Search Console MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add search-console --transport http https://mcpsearchconsole.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcpsearchconsole.com/mcp
~/.codex/config.toml
[mcp_servers.search-console]
url = "https://mcpsearchconsole.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "search-console": {
      "url": "https://mcpsearchconsole.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "search-console": {
      "type": "http",
      "url": "https://mcpsearchconsole.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcpsearchconsole.com/mcp streamable-http sign-in 282 ms 7 min ago

Alternatives to Google Search Console MCP

same job, measured the same way
Google Search Console
by sarahpark

Google Search Console MCP server — search analytics, URL inspection, and sitemaps

121 installs/wk local only
Google Search Console MCP Server
by conorbronsdon

Google Search Console for AI agents: search analytics, sitemaps, URL inspection.

56 installs/wk local only
Google Search Console MCP
by scalably

Read-only Google Search Console MCP: Search Analytics, sitemaps, URL inspection. 5 tools.

132 installs/wk local only
MCP Google Search Console
by crunchtools

Secure MCP server for Google Search Console analytics, sitemaps, and URL inspection

572 installs/wk local only
Gsc
by mikusnuz

MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection

194 installs/wk local only
Google Gsc
by mharnett

Google Search Console MCP: search analytics, URL inspection, site management.

153 installs/wk local only
Google Search Console MCP
by a1-x-tech

MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites.

533 installs/wk local only
Google Search Console
by ni-c

MCP server for Google Search Console: properties, sitemaps, search analytics and URL inspection

153 installs/wk local only

Google Search Console MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for Google Search Console MCP?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Google Search Console MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 201 ms. The bar chart above shows every period we have measured.
How do I connect Google Search Console MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Google Search Console MCP?
No API key is involved. Google Search Console MCP answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Google Search Console MCP?
It answers our handshake in 201 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.