Google Search Console MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 Google Search Console properties available to the configured identity. |
| gsc_get_siteB | Get permission information for one Google Search Console property. |
| gsc_query_search_analyticsC | Query clicks, impressions, CTR, and average position from Google Search Console. Use startRow for pagination. |
| gsc_list_sitemapsC | List sitemaps submitted for a Google Search Console property. |
| gsc_get_sitemapB | Get details about a submitted sitemap. |
| gsc_inspect_urlA | Inspect the version of a URL currently known to Google's index. This does not run a live test or request indexing. |
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 6 tools
Each tool targets a distinct resource and action: sites (list vs permission get), sitemaps (list vs detail get), URL inspection, and search analytics. The list/get pairs are clearly separated by their descriptions, and query_search_analytics and inspect_url have no overlap.
All tools use a uniform gsc_ prefix followed by a consistent verb_noun pattern (list_sites, inspect_url, get_site, query_search_analytics, list_sitemaps, get_sitemap). No style mixing.
Six tools is well-scoped for a Search Console read surface, covering properties, sitemaps, analytics, and URL inspection without redundancy. Each tool earns its place.
Core read operations (list/get sites, list/get sitemaps, analytics query, URL inspection) are covered. Notable gaps exist on the write side: no sitemap submission/deletion and no indexing request, which limits lifecycle coverage but is workable for a read-focused server.