@lomi./gsc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_OAUTH_SCOPE | No | OAuth scope. Default is read-only; set to "write" to enable write permissions. | read |
| GSC_ENABLE_WRITES | No | Set to "true" to enable mutation tools (requires write scope). | false |
| GSC_MCP_TRANSPORT | No | Transport mode. Set to "http" for self-hosted HTTP transport. | stdio |
| GSC_MCP_ALLOWED_HOSTS | No | Comma-separated list of allowed hosts for HTTP transport. | |
| GSC_MCP_ALLOWED_ORIGINS | No | Comma-separated list of allowed origins for HTTP transport. | |
| GSC_MCP_CLIENT_BEARER_TOKEN | No | Bearer token required for non-loopback HTTP transport. | |
| GSC_SERVICE_ACCOUNT_KEY_FILE | No | Path to the Google service account JSON key file for service account authentication. |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsc_capabilitiesA | Return active auth mode, scopes, limits, and disclosure notes for this server. |
| gsc_list_properties | List properties accessible to the configured Google credential. |
| gsc_get_property | Get permission details for one Search Console property. |
| gsc_search_analyticsC | Query clicks, impressions, CTR, and position with dimensions, filters, pagination, and data freshness controls. |
| gsc_performance_overview | Return aggregate clicks, impressions, CTR, position, and daily trend for a recent period. |
| gsc_compare_periodsA | Compare top rows between two date ranges for the same dimensions. |
| gsc_quick_winsB | Identify queries with meaningful impressions, low CTR, and positions in a target range. |
| gsc_inspect_urlB | Inspect one URL indexing status in Google Search Console. |
| gsc_batch_inspect_urls | Inspect up to 20 URLs with bounded concurrency and quota-aware execution. |
| gsc_indexing_issues | Batch inspect URLs and summarize verdicts that look non-indexable. |
| gsc_list_sitemaps | List submitted sitemaps for a Search Console property. |
| gsc_get_sitemap | Get details for one submitted sitemap. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly-performance-review | Review the last 28 days of Search Console performance for one property. |
| low-hanging-opportunities | Find quick-win queries with meaningful impressions and weak CTR. |
| cannibalization-analysis | Look for multiple pages competing for the same query. |
| indexing-audit | Inspect a set of important URLs and summarize indexing blockers. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| capabilities | Active auth mode, scopes, limits, and disclosures. |
| limits | Documented quotas and output limits for this server. |
| sites | Properties visible to the configured Google credential. |
TDQS
Scored across 5 tools
Each tool has a distinct purpose: capabilities (metadata), search analytics (raw data), quick wins (heuristic analysis), compare periods (comparative analysis), inspect URL (individual URL status). No overlap.
All tools start with 'gsc_' and follow a verb_noun or noun phrase pattern. Most are nouns or adjective-noun (e.g., quick_wins), while compare_periods and inspect_url use verbs. Consistent prefix but minor variation in verb usage.
5 tools is appropriate for a focused GSC server covering analytics, insights, and URL inspection. Not overly many nor too few, though additional tools could be justified.
Covers core search analytics and URL inspection, but missing tools for sitemap management, index coverage, site listing, or mobile usability. Notable gaps for a full GSC integration.