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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sudomichael/search-console-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server