mcp-search-console
Related Servers
Alternatives to mcp-search-console
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to query and manage Google Search Console data, including search analytics, URL indexing status, and sitemap management, for SEO and LLMO analysis directly from a conversation.152,991 npmMIT
- AlicenseAqualityDmaintenanceConnects AI assistants to Google Search Console data for SEO analysis, including search analytics, URL inspection, sitemaps, indexing, and opportunity detection.17MIT
- AlicenseAqualityCmaintenanceConnects 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access Google Search Console search performance and index health data, including clicks, impressions, rankings, URL inspection, and sitemap management.10 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to query and analyze Google Search Console data, including search analytics, URL inspection, sitemaps, and property verification, and to perform actions like submitting sitemaps and adding properties through natural language.199 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides 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.42 npm7MIT
TDQS
Scored across 21 tools
Multiple tools have heavily overlapping purposes: get_sitemaps, list_sitemaps_enhanced, get_sitemap_details, and manage_sitemaps all cover sitemap listing/details, while get_search_analytics, get_advanced_search_analytics, get_performance_overview, and compare_search_periods all provide overlapping analytics views. This makes it genuinely ambiguous which tool an agent should select for a given task.
Most tool names use snake_case and a verb_noun pattern, but the set mixes get_ and list_ for similar operations (get_sitemaps vs list_sitemaps_enhanced) and uses inconsistent patterns like inspect_url_enhanced vs batch_url_inspection. The naming is readable but not predictable enough to guide tool selection.
At 21 tools, the server is on the heavy side for a single-domain MCP server. Many tools are justified by GSC's broad feature set, but redundant sitemap and analytics tools inflate the count beyond what is necessary. The set could be trimmed to roughly 12-15 tools without losing real capability.
The tool surface covers property management, search analytics, sitemap lifecycle, URL inspection, indexing checks, and authentication—covering most major Search Console workflows. Minor gaps exist, such as no direct URL indexing submission or property update operation, but agents can generally work around them.