GSC MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GSC_OAUTH_TOKEN_PATH | No | Path to the OAuth token file (e.g., .gsc-token.json). | |
| GSC_OAUTH_CREDENTIALS_PATH | No | Path to the OAuth client JSON file for Google OAuth 2.0. | |
| GSC_SERVICE_ACCOUNT_KEY_PATH | No | Path to the JSON key file for a Google service account. |
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 the authenticated account has access to in Google Search Console. |
| query_search_analyticsA | Query Google Search Console performance data (clicks, impressions, CTR, position) for a site, broken down by dimensions like query, page, country, device, or date. |
| list_sitemapsA | List all sitemaps submitted for a Search Console property. |
| get_sitemapA | Get details and status for a single sitemap. |
| submit_sitemapB | Submit a new sitemap to Google Search Console for a property. |
| delete_sitemapA | Remove a sitemap from Google Search Console for a property. |
| inspect_urlA | Run the Search Console URL Inspection tool on a single URL to check indexing status, coverage issues, mobile usability, and more. |
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
Each tool targets a distinct resource and action: site listing, sitemap lifecycle (list/get/submit/delete), URL inspection, and search analytics querying. No overlap; get_sitemap vs list_sitemaps is clearly singular vs plural.
All tool names follow a consistent verb_noun pattern: list_sites, get_sitemap, submit_sitemap, delete_sitemap, inspect_url, query_search_analytics, list_sitemaps. The style is uniform and predictable.
7 tools is well-scoped for a Google Search Console server, covering the core resources (sites, sitemaps, URLs, analytics) without bloat. Each tool earns its place.
The sitemap lifecycle is complete (list, get, submit, delete), and URL inspection plus search analytics cover major GSC functions. A minor gap is the lack of a dedicated tool to get detailed property info beyond listing, but this is workable.