Google's Search Console API Fails Silently, So I Built an MCP Server That Doesn't

Description and use

The open‑gsc‑mcp MCP server eliminates silent Search Console API failures, offers clear error messages, logs requests, and provides traffic analysis tools.

Problem

Google Search Console API silently returns empty results for malformed or edge‑case requests, making it hard to distinguish a broken query from a legitimate zero‑traffic period, especially for AI assistants that cannot detect the error.

Outcome

The MCP server eliminates silent API failures, provides explicit error messages, logs requests, and offers analytical tools, improving reliability and insight for Search Console users.

Workflow

• 1. Install uv and open‑gsc‑mcp via uvx. 2. Authenticate with Google using OAuth client. 3. Add the MCP server to an MCP client (Claude Code, Claude Desktop, Cursor). 4. Issue natural language queries; the server validates, calls the API, and returns structured data. 5. Use explain_change to split traffic changes by dimension. 6. Run audit_indexing to rebuild page indexing reports within the 2,000‑URL daily quota.

Evidence

Ask the Google Search Console API for clicks filtered by country us and you get zero rows. No error, no warning, just nothing.

Source

I built an MCP server for Search Console that checks for these cases before the call goes out and tells you in plain words what's wrong.

Source

Every analytics result includes the exact request sent to Google, so you can see what was actually asked.

Source