Search Console MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_APPLICATION_CREDENTIALS | No | The path to your Google Cloud Service Account JSON key file. Required for the alternative service account authentication flow. |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_startedA | Start here. Returns a complete map of this server's capabilities, active platforms, and recommended workflows. Call this once at the beginning of any session. |
| sites_listA | List verified web properties across Google Search Console, Bing Webmaster Tools, or GA4. |
| sites_manageB | Add or delete a web property from Google Search Console or Bing Webmaster Tools. |
| accounts_manageC | Manage Google Search Console service accounts and site permissions. |
| sitemaps_listB | List submitted XML sitemaps and status for a site. |
| sitemaps_submitB | Submit a new XML sitemap to Google Search Console and/or Bing Webmaster Tools. |
| sitemaps_deleteA | Delete a sitemap from Google Search Console or Bing Webmaster Tools. |
| analytics_queryB | Unified search performance query replacing single-dimension tools. Supports queries, pages, countries, devices, and search appearances. |
| analytics_compareB | Period-over-period search performance comparisons, trends, and traffic drop attributions. |
| analytics_anomaliesB | Detect search traffic anomalies across Google and Bing. |
| analytics_advancedC | Google Analytics 4 (GA4) e-commerce, realtime metrics, user behavior, and conversion funnels. |
| genai_query_insightsA | Detect likely generative-AI / AI-Mode / conversational fanout queries across Google and Bing. Because neither search engine exposes generative-AI citation data via its public API yet, this matches heuristic patterns (prompt verbs, follow-ups, conversational phrasing) on regular query-level performance data; it is an undercount, not an official report. |
| adsense_accountsA | List configured AdSense publisher accounts, or discover all publisher accounts the authorized user has access to. |
| adsense_reportB | Google AdSense earnings & performance report: estimated earnings, impressions, clicks, CTR and RPM with dimension breakdowns. |
| adsense_payments_alertsB | Outstanding AdSense payments and account alerts (policy issues, payment holds). |
| inspection_inspectB | Inspect indexing, canonical, and crawl status for single or batch URLs on Google or Bing. |
| pagespeed_analyzeB | Run PageSpeed Insights & Core Web Vitals performance analysis for a page. |
| indexing_submitB | Submit URL(s) for indexing via Google Indexing API, Bing URL submission, or IndexNow protocol. |
| indexing_statusA | Check notification status for Google Indexing API or remaining daily Bing submission quota. |
| seo_auditB | Specialized SEO intelligence analysis (recommendations, quick wins, cannibalization, striking distance, lost queries, low CTR, brand vs nonbrand). |
| seo_keywords_researchC | Keyword performance stats, related query expansion, and search volume estimates. |
| schema_validateA | Validate structured data (JSON-LD, Microdata, RDFa) for a given webpage URL. |
| site_health_checkC | Comprehensive health audit across Google Search Console and Bing Webmaster Tools. |
| compare_enginesB | Cross-engine performance matrix comparing Google Search Console vs Bing Webmaster Tools. |
| diagnosticsA | Run connectivity diagnostics for all connected accounts. Use this to troubleshoot '0 results' or authentication issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate_traffic_drop | |
| find_quick_wins | |
| full_site_audit | |
| analyze_page | |
| platform_comparison | |
| content_opportunity_report | |
| executive_summary | |
| ga4_traffic_audit | |
| adsense_earnings_review | |
| adsense_monetization_audit | |
| seo_traffic_detective | |
| seo_striking_distance | |
| seo_cannibalization_audit | |
| seo_compare_google_bing |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| google-algorithm-updates | Comprehensive timeline of Google Search Core Updates and Spam Policy updates (2024-2026). |
| connected-sites | List of configured Google Search Console, Bing Webmaster Tools, GA4 properties, and AdSense publisher accounts. |
| adsense-accounts | Configured Google AdSense publisher accounts. |
| adsense-payments | Outstanding AdSense payments balance and active account alerts, keyed by configured account ID. |
| backward-compatibility-map | Migration mapping table for legacy tool names to Search Console MCP v2.0 Fluent Domain Tools. |
TDQS
Scored across 25 tools
Most tools target distinct resources (sitemaps, indexing, sites, AdSense), but the analytics/audit cluster is fuzzy: site_health_check, seo_audit, analytics_anomalies, and analytics_compare all overlap around diagnosing traffic/health issues. Descriptions help separate them, but an agent could still hesitate between health check, audit, anomaly detection, and period comparison.
Tool names mix conventions unpredictably: some are noun_verb (sites_manage, sitemaps_submit), some verb_noun (compare_engines), some bare nouns (diagnostics, get_started), and some are redundant (inspection_inspect). This makes it hard to guess the correct tool name from the pattern.
With exactly 25 tools, the server sits at the heavy end of the borderline range. The breadth partially justifies the count since it covers Search Console, Bing, GA4, AdSense, PageSpeed, and schema validation, but many adjacent concerns are exposed as individual tools rather than consolidated surfaces.
The core Search Console/Bing workflows are well covered: site management, sitemaps CRUD, performance analytics, URL inspection, indexing submission, and status checks. Minor gaps exist (e.g., no URL removal tool or GSC message/alerts surface), but nothing creates a dead end in normal SEO diagnostic workflows.