search-console-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEARCH_CONSOLE_MCP_CLIENT_ID | No | Your own Google OAuth client ID (optional, overrides built-in credentials) | |
| SEARCH_CONSOLE_MCP_CLIENT_SECRET | No | Your own Google OAuth client secret (optional, overrides built-in credentials) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_propertiesA | List the Google Search Console properties this account can access. Call this first to get exact siteUrl values (e.g. 'sc-domain:example.com' or 'https://example.com/'). |
| query_search_analyticsA | Query real Search Console performance data: clicks, impressions, CTR, and average position, grouped by the dimensions you choose. Dates are YYYY-MM-DD (GSC data lags ~2-3 days). Use dimensions like ['query'], ['page'], ['query','page'], or ['date'] for trends. |
| compare_periodsA | The biggest-movers analysis, computed for you: this date range vs the prior equal-length range, joined per page (or query) with clicks/impressions/position deltas, sorted by biggest change. Use this for 'what fell/grew', 'this month vs last', and trend diagnosis — it's one call and the math is already done. |
| inspect_urlA | Google's index status for one URL: is it indexed, why not, canonical chosen by Google, last crawl, mobile/rich-result issues. |
| inspect_urlsA | Batch index-status check: up to 10 URLs in one call (per-URL errors reported inline). Use for indexing audits instead of ten single calls. |
| list_sitemapsA | List submitted sitemaps for a property, with status and counts. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cannibalization_check | Find queries where two of your pages compete against each other — and which page should win |
| seo_checkup | Full health check: trend, biggest movers, and the top 3 moves worth making |
| striking_distance | Queries sitting just off page 1 — the fastest traffic you're not getting |
| traffic_drop | Diagnose a traffic drop: what fell, where, and the most likely cause |
| indexing_audit | Are your important pages actually indexed? Sitemaps + index status |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of Google Search Console: trend analysis, URL index checks (single and batch), property listing, sitemap listing, and performance data querying. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., inspect_url, list_properties, query_search_analytics). No mixing of conventions.
With 6 tools, the server is well-scoped for common Search Console tasks. The count is neither too small nor too large for the domain.
The set covers essential CRUD-like operations (list properties, list sitemaps, inspect URLs, query data, compare periods). Minor gaps exist, such as lacking tools for sitemap submission or crawl rate management, but the core workflows are supported.