Google Search Console MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_SERVICE_ACCOUNT_FILE | Yes | The path to the JSON key for the Google Cloud service account used to authenticate with the Google Search Console API. For example, ~/.config/gcloud/gsc-service-account.json. Use absolute paths in desktop clients since they do not expand ~ or inherit your shell's PATH. |
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 |
|---|---|
| list_sitesA | List Search Console properties the service account has access to, with the permission level for each. |
| search_analyticsA | Query Search Analytics (clicks, impressions, CTR, position). Args: site: Property URL, e.g. 'sc-domain:example.com' or 'https://example.com/'. start_date / end_date: YYYY-MM-DD. Defaults to the last 28 days ending 2 days ago. dimensions: Any of date, query, page, country, device, searchAppearance. Omit for site-wide totals. row_limit: 1-25000 (default 100). Use start_row to paginate. filters: List of {"dimension": "query|page|country|device|searchAppearance", "operator": "equals|contains|notContains|includingRegex|excludingRegex", "expression": "..."}. Multiple filters are ANDed. search_type: web (default), image, video, news, discover, googleNews. |
| compare_periodsB | Compare two date ranges side by side with deltas. With no dimension, returns site-wide totals for both periods. With a dimension (query, page, country, device), returns the top rows by current clicks with previous-period values and deltas; rows that only exist in one period are included with zeros for the other. |
| list_sitemapsB | List submitted sitemaps for a property with status, last download, errors/warnings and indexed URL counts. |
| inspect_urlB | Run URL Inspection for a page: index status, coverage verdict, canonical (Google vs user), last crawl, robots/indexing state, mobile and rich-result verdicts. Quota: 2000 calls/day per property. Requires Owner or Full access. |
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 5 tools
Each tool has a distinct purpose: list_sites, search_analytics, compare_periods, list_sitemaps, inspect_url. Potential minor confusion between search_analytics and compare_periods (both query analytics data), but descriptions clarify the difference (single vs two periods).
All tool names follow a consistent verb_noun pattern (list_sites, search_analytics, compare_periods, list_sitemaps, inspect_url). No deviations or mixing of conventions.
5 tools is well-scoped for a Google Search Console server, covering core operations without bloat. Each tool serves a clear purpose.
Covers listing sites, analytics, sitemaps, and URL inspection, but missing operations for managing sitemaps (submit, delete) and site property management (add, delete). These gaps could cause agent dead ends for common tasks.