Connect Search Console to any MCP client

The endpoint

The server lives at /mcp on the app domain and speaks Streamable HTTP at protocol version 2025-06-18. Clients POST JSON-RPC, send an initialize request, then tools/list. There is nothing to install and no local proxy in the path.

• Authorization: Bearer with a key of the form apk_live_ plus 32 hex characters
• Keys are shown once at creation and stored only as a SHA-256 hash
• Every call updates the key last-used timestamp and request counter

The 19 tools

Small enough that a model picks the right one reliably, which matters more than catalogue size.

• Discovery: list_properties, search_analytics
• Performance: top_queries, top_pages, top_countries, compare_periods
• Diagnosis: content_decay, cannibalization, ctr_benchmark, page_poaching, rank_changes, new_lost_rankings
• Indexing: url_inspection, sitemaps
• Timeline: annotations, and create_annotation on a write key
• Analytics: ga4_overview, ga4_breakdown, ga4_key_events

Dates are optional

Omit the range on any tool and the server uses the last 28 settled days, accounting for the Search Console reporting lag, with the comparison window defaulting to the previous period of the same length. The client never has to know today's date to ask a sensible question.

Scopes and rate limits

A key is read-only or read and write. A read-only key cannot reach a write tool at all, and every mutation on a write key is audit-logged.

• 60 requests per minute per key, 1,000 per hour per account
• Over the limit returns HTTP 429 with Retry-After in seconds
• Revoke a single key without touching the rest of the account

REST, if you prefer

The same tools are exposed as GET and POST routes under /v1 with a generated OpenAPI 3.1 document at /v1/openapi.json, which doubles as a function-calling spec. Same keys, same scopes, same limits.