gsc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_MCP_TOKEN | No | Path to cached access token (auto-managed) | ~/.config/gsc-mcp/token.json |
| GSC_MCP_CREDENTIALS | No | Path to OAuth client JSON from Google Cloud | ~/.config/gsc-mcp/credentials.json |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsc_list_sitesA | List every Google Search Console property the authenticated user can access. Returns a table of site URLs and permission levels. Use the exact siteUrl string returned here when calling other tools — the format matters (domain properties use 'sc-domain:example.com' prefix). |
| gsc_query_search_analyticsA | Run a flexible Search Analytics query against a property. This is the general-purpose analytics tool. For common cases, prefer the
convenience tools Returns clicks, impressions, CTR and average position per row. |
| gsc_top_queriesA | Return the top N search queries for a site over a recent period. Convenience wrapper over gsc_query_search_analytics. Use this when you want a quick ranking of which queries are driving impressions/clicks — ideal for weekly SEO check-ins. |
| gsc_top_pagesA | Return the top N landing pages for a site over a recent period. Convenience wrapper over gsc_query_search_analytics. Use this to spot which URLs drive the most organic traffic and which are underperforming. |
| gsc_inspect_urlA | Run the URL Inspection API for a specific page. Returns indexing verdict, coverage state, last crawl time, Google-chosen canonical, mobile usability, rich results — everything the Inspect URL panel in Search Console shows. Use this to diagnose why a page isn't ranking, confirm indexing after a publish, or spot canonical mismatches. Rate limit: ~2000 calls per property per day. For bulk inspections, add a sleep between calls (a future bulk tool will handle this). |
| gsc_list_sitemapsA | List every sitemap registered for a property, with status and error counts. Useful for: verifying a sitemap was accepted, spotting sitemaps that have parse errors, and confirming fresh submission dates. |
| gsc_health_checkA | Diagnostic: confirm the OAuth token is valid and the Search Console API is reachable. Run this first when setting up the server or after errors to determine whether the issue is auth, network, or a specific site. |
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 7 tools
Each tool has a clearly distinct purpose: health check, URL inspection, sitemap listing, site listing, and three levels of analytics (general, top pages, top queries). No overlap that would confuse an agent.
All tools follow a consistent 'gsc_underscore' pattern with descriptive names (e.g., gsc_health_check, gsc_inspect_url, gsc_top_queries). No mixing of conventions.
7 tools cover key Search Console functionalities (health, inspection, sitemaps, sites, analytics) without being excessive. The scope is well-mapped to the domain.
Common read operations are present, but write/mutate tools are missing (e.g., no submit or delete sitemap, no request indexing, no site removal). This creates notable gaps for complete lifecycle management.