gsc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_CLIENT_ID | No | Google OAuth Desktop app client ID, used when authenticating with `gsc auth`. | |
| GSC_TOKEN_FILE | No | Path to the OAuth token file. Defaults to ~/.config/gsc-mcp/token.json. | |
| GSC_ALLOW_WRITE | No | Set to 1 to allow write operations and expose the submit_sitemap tool. Default is read-only. | |
| GSC_CLIENT_SECRET | No | Google OAuth Desktop app client secret, used when authenticating with `gsc auth`. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to a service-account JSON file to use as an alternative to OAuth token 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List Search Console properties accessible to your account |
| search_analyticsC | Query top Search Console rows; compare with the equal previous period |
| inspect_urlB | Inspect Google indexed URL status (not a live test) |
| list_sitemapsC | List submitted sitemaps |
| striking_distanceD | Search Console insight: striking_distance |
| low_ctrD | Search Console insight: low_ctr |
| cannibalizationD | Search Console insight: cannibalization |
| moversD | Search Console insight: movers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
The core tools (list_sites, search_analytics, inspect_url, list_sitemaps) are clearly distinct, but the four insight tools have tautological descriptions ("Search Console insight: striking_distance") that give no real explanation, forcing the agent to infer meaning from names. All five analytics-related tools draw from the same underlying Search Console data, so the boundary between search_analytics and striking_distance/low_ctr/movers/cannibalization is unclear.
Four tools follow a clean verb_noun convention (list_sites, search_analytics, inspect_url, list_sitemaps) while the four insight tools are bare noun phrases (striking_distance, low_ctr, cannibalization, movers). The style split is systematic but still breaks predictability about whether a tool is an action or a report.
Eight tools is a well-scoped size for a Search Console analytics server, with room for site/sitemap listing, querying, inspection, and canned insights. Nothing feels padded or missing at the count level.
The surface covers discovery (sites, sitemaps), reporting (search_analytics), and inspection, but sitemaps are read-only — no submit or delete operation — and sites cannot be added or removed. For a diagnostics-oriented server this is workable, but sitemap submission is a standard Search Console operation that agents will hit as a dead end.