gsc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port (default 8080). | 8080 |
| BASE_URL | No | Public URL of the service. Used for OAuth metadata and as the canonical resource URI tokens are bound to. (Mode B) | |
| LOG_LEVEL | No | Python log level (default INFO). | INFO |
| GCP_PROJECT_ID | No | GCP project hosting Firestore. (Mode B) | |
| MCP_USER_EMAIL | No | Your email — set in Claude Desktop config. (Mode A) | |
| ALLOWED_DOMAINS | No | Comma-separated email domain allowlist (e.g. acme.com,beta.com). Empty = no restriction. | |
| GOOGLE_CLIENT_ID | No | Google OAuth client ID. (Mode B) | |
| OAUTH_CONFIG_PATH | No | Path to client_secret.json. Alternative to GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. | |
| GOOGLE_REDIRECT_URI | No | Override the Google callback URL. Defaults to ${BASE_URL}/auth/callback. | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret. (Mode B) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_propertiesA | List all GSC properties the authenticated user has access to, with permission levels. |
| get_site_detailsA | Get details for a specific GSC property including permission level. |
| add_siteA | Add a new property to GSC. Requires site owner verification. |
| delete_siteB | Remove a property from GSC. Irreversible — use with caution. |
| get_search_analyticsC | Query GSC search analytics data. |
| get_performance_overviewC | Get a summary of clicks, impressions, CTR, and average position for a property. |
| compare_periodsC | Compare search performance between two date periods. |
| get_position_band_reportC | Get pages filtered by position band. |
| get_ctr_optimization_reportA | Find pages with high impressions but low CTR — quick-win optimization candidates. |
| get_keyword_cannibalizationC | Identify queries where multiple pages are competing for the same keyword. |
| batch_search_analyticsA | Run multiple search analytics queries in one call. |
| export_full_datasetB | Export all rows bypassing the 5,000-row API limit using pagination. |
| inspect_urlB | Inspect a single URL for indexing status, mobile usability, rich results, and AMP. |
| batch_url_inspectionC | Inspect multiple URLs for indexing status, mobile usability, and rich results. |
| list_sitemapsA | List all sitemaps for a property with indexing stats and health classification. |
| get_sitemapA | Get details for a specific sitemap. |
| submit_sitemapB | Submit a sitemap to Google Search Console. |
| delete_sitemapA | Remove a sitemap from GSC. Does not delete the actual sitemap file. |
| analyze_site_healthC | One-call site health report: top pages with traffic, indexing status, mobile usability, and last crawl time. |
| identify_quick_winsA | Find pages worth quick optimization: high impressions, low CTR, ranked 4-10, no indexing issues. |
| crawl_error_summaryB | Aggregate crawl and indexing errors across a property's sampled pages. |
| property_migration_checklistB | Generate a migration checklist when moving a site. |
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 22 tools
Most tools target distinct resources and actions, but identify_quick_wins and get_ctr_optimization_report both describe the same high-impressions/low-CTR quick-win use case, creating selection ambiguity. Additionally, analyze_site_health and crawl_error_summary both touch on indexing/crawl health, which may confuse an agent.
The vast majority of tools follow a clear verb_noun pattern (list_properties, add_site, submit_sitemap, delete_site). A few names like crawl_error_summary and property_migration_checklist deviate from this pattern, but they are still readable and do not disrupt the overall convention.
At 22 tools, this is in the 'heavy' range (16-25), though the Google Search Console domain legitimately spans property management, search analytics, URL inspection, sitemaps, and crawling health. Each tool occupies a mostly distinct niche, so the count is defensible but slightly higher than ideal.
The set covers the major GSC workflows: property CRUD, search analytics reporting with comparisons and filters, URL inspection, sitemap management, and crawl error summaries. Minor gaps exist (e.g., no detailed per-URL crawl error listing or permission management), but agents can complete common tasks without dead ends.