Google Search Console MCP Server
Related Servers
Alternatives to Google Search Console MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConnects Google Search Console to AI assistants, enabling natural language queries for SEO data, indexing audits, sitemap management, and full site audits.20MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to analyze Google Search Console SEO data through natural language, including search analytics, URL inspection, sitemap management, and property management.21MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to Google Search Console so users can query search analytics, compare performance periods, inspect URL indexing status, and manage sitemaps and properties through natural language.MIT
- AlicenseBqualityDmaintenanceConnects Google Search Console to AI assistants, enabling SEO data analysis through natural language conversations.32MIT
- AlicenseNot gradedqualityDmaintenanceConnects Google Search Console to AI assistants, enabling SEO data analysis via natural language conversations.MIT
- AlicenseAqualityDmaintenanceConnects Google Search Console to AI assistants, enabling natural language analysis of SEO data. Provides read-only tools for properties, search analytics, URL inspection, and sitemaps.15MIT
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes: sitemap management, URL inspection, analytics queries, and specific diagnostics are all separated cleanly. The only real ambiguity is among the analytics-analysis tools like find_opportunities, diagnose_traffic_drops, and content_decay, though their descriptions give enough differentiation.
Snake_case is consistent, and clusters like submit_sitemap/list_sitemaps/delete_sitemap follow a clear verb_noun pattern. However, several diagnostic tools use bare nouns (cannibalization, content_decay, ctr_benchmarks, topic_clusters) and search_analytics/verify_claim break the action-oriented naming convention.
At 17 tools, the server is slightly above the ideal 3-15 range, but the breadth is justified by covering four distinct GSC areas: sitemaps, indexing, raw analytics, and SEO diagnostics. Each tool addresses a specific use case and there is little obvious filler.
Core GSC workflows are covered well: sitemap CRUD, single and batch URL inspection, indexing notification status, and search analytics with period comparison and diagnostic helpers. Minor gaps exist, such as no property create/delete and no broader GSC reports like links or Core Web Vitals, but common SEO tasks can be completed without dead ends.