Google Search Console MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CLIENT_ID | No | Google OAuth client ID, used as an override for stored credentials. | |
| GOOGLE_ACCESS_TOKEN | No | Google access token for quick tests. | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret, used as an override for stored credentials. | |
| GOOGLE_REFRESH_TOKEN | No | Google OAuth refresh token, used as an override for stored credentials. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to Application Default Credentials 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gsc_list_sitesA | List all Search Console properties available to the authenticated Google account. |
| gsc_search_analyticsC | Run a Search Analytics query for one property, selected properties, or all properties. Returns clicks, impressions, CTR, and average position. |
| gsc_top_queriesC | Fetch top query rows for one property, selected properties, or all properties. Supports filters for query, page, country, and device. |
| gsc_search_appearance_typesA | Discover searchAppearance values available for a property. Use these values to filter later Search Analytics calls. |
| gsc_keyword_opportunitiesB | Find high-impression, low-CTR queries across one or many properties. Returns clicks, impressions, CTR, and position sorted by impressions. |
| gsc_list_sitemapsC | List submitted sitemaps for a Search Console property. |
| gsc_get_sitemapC | Fetch status and metadata for a submitted sitemap. |
| gsc_submit_sitemapB | Submit a sitemap URL to a Search Console property. Requires the webmasters OAuth scope. |
| gsc_delete_sitemapC | Remove a submitted sitemap from a Search Console property. Requires the webmasters OAuth scope. |
| gsc_batch_submit_sitemapsA | Submit up to 100 sitemap URLs across multiple Search Console properties. Each target reports success or its Google API error. Requires the webmasters OAuth scope. |
| gsc_batch_delete_sitemapsA | Delete up to 100 submitted sitemap URLs across multiple Search Console properties. Each target reports success or its Google API error. Requires the webmasters OAuth scope. |
| gsc_inspect_urlB | Inspect the indexed status of a URL under a Search Console property. |
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 12 tools
Most tools are clearly distinct (sites, inspection, sitemap CRUD), but there is meaningful overlap among gsc_search_analytics, gsc_top_queries, and gsc_keyword_opportunities, all of which return query-level performance data. Single and batch sitemap tools also overlap, though they are separable by operation scope.
All tool names use a consistent gsc_ prefix and snake_case convention, which is predictable. However, some names are verb-noun (list_sites, delete_sitemap) while others are noun-only (top_queries, keyword_opportunities), creating minor stylistic inconsistency.
Twelve tools is well-scoped for a Search Console server covering site listing, URL inspection, sitemap management, and search analytics. Each tool has a defensible place in the overall surface without feeling padded or redundant.
The tool surface covers the major Search Console workflows: property discovery, URL inspection, sitemap submission/deletion/status, and search performance analysis. Minor gaps like per-property detail retrieval or richer analytics dimensions exist but are workable around.