Google Search Console MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_APPLICATION_CREDENTIALS | Yes | Absolute path to the Google Cloud service account JSON key file. This service account must be added as a user on each Search Console property you want to access. |
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 all sites (properties) you have access to in Google Search Console. |
| search_analyticsB | Query search analytics data from Google Search Console. Returns clicks, impressions, CTR, and position for your site. |
| inspect_urlB | Inspect a URL to check its indexing status, crawl info, and any issues Google found. |
| list_sitemapsA | List all sitemaps submitted for a site in Google Search Console. |
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 4 tools
Each tool targets a distinct Google Search Console resource and action: site listing, analytics queries, URL inspection, and sitemap listing. There is no overlap in purpose, so an agent can easily select the right tool for a given task.
All tools follow a consistent verb_noun pattern in lowercase snake_case (list_sites, search_analytics, inspect_url, list_sitemaps). The naming is predictable and uniform across the entire set.
Four tools is a reasonable size for a focused read-only Search Console server. It is slightly lean but each tool covers a distinct core function, and the count feels appropriate for the apparent scope.
The server covers primary read operations but misses common management actions like submitting or deleting sitemaps. Analytics and URL inspection are present, but there is no sitemap submission or deeper detail (e.g., sitemap errors), leaving notable gaps for workflows.