Google Search Console (GSC) MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_CREDENTIALS_PATH | No | Path to the Google Search Console credentials JSON file. Defaults to ~/.config/gws/searchconsole_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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsc_list_sitesA | List the Search Console properties (sites) the signed-in Google account can access, with each one's permission level. This is the entry point: every other tool needs a property string in the exact form returned here. |
| gsc_search_analyticsA | Query Search Console search analytics for a property over a date range: clicks, impressions, CTR, and average position, grouped by the dimensions you pass (query, page, country, device, date). Returns compact rows. Use this for 'what are my top queries / pages' and trend questions. GSC data lags ~2-3 days, so end your range a few days before today. |
| gsc_striking_distanceA | The SEO goldmine view: queries ranking just off page one (average position 8-25) with enough impressions to be worth optimizing. These are the keywords where a small content tweak can win real clicks. Computed client-side from search analytics; returns queries sorted by impressions. |
| gsc_list_sitemapsA | List the sitemaps submitted for a property, with each one's submit/download times, pending state, and warning/error counts. Use this to check whether a sitemap was processed and is error-free. |
| gsc_submit_sitemapA | Submit (or re-submit) a sitemap to Google Search Console for a property. This is a WRITE action: it registers the sitemap and pings Google to crawl it. Requires the full webmasters OAuth scope — if the saved credential is read-only, re-mint with scripts/seo-auth-setup.py. Idempotent: re-submitting the same sitemap URL just refreshes it. |
| gsc_delete_sitemapA | Remove a sitemap from a property in Search Console. This is a DESTRUCTIVE write action: it deregisters the sitemap (it does not delete the file from your server, but Google stops tracking it). Requires the full webmasters OAuth scope. |
| gsc_inspect_urlA | Inspect a single URL with the URL Inspection API: whether Google has it indexed, its coverage state, last crawl time, Google's chosen canonical, and a one-line mobile/rich-results summary. Returns a compact projection, not the full raw blob. Use this to debug 'why isn't this page indexed'. |
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
Most tools target distinct resources and actions, but gsc_search_analytics and gsc_striking_distance both expose query performance data, with striking_distance being a derived view that could cause confusion. The clear descriptions mitigate this, but an agent might select the wrong one for a generic analytics request.
The gsc_ prefix and verb_noun pattern are used consistently across most tools, but gsc_striking_distance deviates from the verb-first convention, being an adjective/noun phrase. This minor inconsistency does not impede readability.
Seven tools cover the GSC domain without bloat or thinness. Each tool has a clear purpose and fits within the ideal 3-15 range.
The server covers the core GSC lifecycle: site listing, search analytics, sitemap management (list/submit/delete), and URL inspection. No major workflow appears missing for practical SEO use cases.