Google Search Console MCP Server
Related Servers
Alternatives to Google Search Console MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to analyze Google Search Console SEO data through natural language, including search analytics, URL inspection, sitemap management, and property management.21MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to Google Search Console data for SEO analysis, including search analytics, URL inspection, sitemaps, indexing, and opportunity detection.17MIT
- AlicenseAqualityBmaintenanceRank by Ouroboros Apps (https://ouroborosapps.com). SEO rankings from Google Search Console, read-only: top queries and pages, traffic trends, period comparisons, quick wins, dropped pages, and URL inspection. Connect by pasting https://rank.ouroborosapps.com/mcp into Claude, Cursor, Grok, or ChatGPT developer mode (OAuth). Docs: https://ouroborosapps.com/docs/rank9MIT
- AlicenseAqualityDmaintenanceProvides read-only access to Google Search Console data, allowing AI assistants to query site performance metrics like keywords, clicks, and rankings using natural language. It supports listing verified properties, querying search analytics with dimension filters, and retrieving sitemap information.31MIT
- AlicenseAqualityAmaintenanceProvides AI agents with read-only access to Google Search Console data, including search analytics, index coverage, and sitemap status. It enables users to query clicks, impressions, and ranking performance or check URL indexing status through natural language.466 npm9MIT
- AlicenseAqualityAmaintenanceProvides AI assistants with live access to Google Search Console search analytics, URL inspection, and sitemap management through real API calls.10MIT
TDQS
Scored across 15 tools
Multiple tools have overlapping purposes, such as list_sitemaps vs list_sitemaps_enhanced, and get_search_analytics vs get_advanced_search_analytics. The descriptions help but the boundaries are unclear, especially for batch_url_inspection vs check_indexing_issues.
Tool names generally follow the verb_noun pattern (list_properties, get_search_analytics, compare_search_periods). Minor deviations like batch_url_inspection and the 'enhanced' suffix in inspect_url_enhanced/list_sitemaps_enhanced cause slight inconsistency but overall naming remains predictable.
15 tools is at the upper boundary of the ideal range but appropriate for the scope of GSC. However, several tools could be merged (e.g., analytics variants, sitemap listers), making the count slightly inflated.
The server covers the main GSC features: properties, analytics, sitemaps, and URL inspection. Minor gaps exist (e.g., no write actions like submitting sitemaps), but for a read-only server, the coverage is solid. The redundant tools actually add some completeness to specific use cases.