search-console-mcp
Related Servers
Alternatives to search-console-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to access Google Search Console data including search performance, URL indexation, sitemaps, and built-in SEO analysis tools such as trending queries, cannibalization detection, and traffic drop diagnostics.148 npm11MIT
- AlicenseBqualityCmaintenanceConnects Claude to Google Search Console, GA4, Bing Webmaster Tools, IndexNow, PageSpeed Insights, AdSense and Google Ads Keyword Planner, plus live technical SEO audits of pages and sitemaps. Users ask plain-language questions about traffic drops, index status, canonicals, AI referral traffic and keyword volumes, and answers are pulled live from the APIs in real time.2827 npmMIT
- AlicenseCqualityCmaintenanceEnables Claude Code to read Google Search Console and GA4 data locally with read-only access, and provides combined SEO analysis tools for comparing datasets and identifying opportunities.20MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying Google Search Console data from Claude Desktop, including site listing, sitemap status, search analytics by query/page/country/device/date, and single-URL index inspection through read-only OAuth access.148 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables users to query Google Search Console data interactively from Claude Desktop and via CLI, providing search analytics, period comparisons, branded split, indexing status, sitemaps, and full CSV exports.-
- AlicenseAqualityCmaintenanceEnables Claude to query Google Search Console performance data, inspect URL indexing status, submit URLs via IndexNow, and check title and meta-description lengths against Bing limits directly in chat.6MIT
TDQS
Scored across 44 tools
Most tools occupy distinct slots: performance_query vs performance_overview vs compare_periods are clearly layered, and the robots_txt_* family separates check/history/diff/test/watch cleanly. A few clusters blur together — property_overview vs weekly_report vs multi_site_dashboard, and inspect_url vs diagnose_url vs run_inspections vs inspection_job — but the descriptions do enough to steer selection.
Everything is snake_case with recognizable domain prefixes (robots_txt_*, queue_from_*, check_*, list_*, find_*) and no camelCase or style mixing. However, only about half the names follow the verb_noun pattern; many are bare nouns (server_status, content_decay, traffic_drops, cron_stats, image_audit), which weakens predictability.
44 tools is a large surface for one server, and several are convenience wrappers over combinations of other tools (weekly_report, multi_site_dashboard, property_overview, verify_metric). While the domain genuinely spans performance, indexing, robots.txt, technical SEO and logs, the count pushes well past a comfortably scannable set.
Coverage is unusually thorough: performance analytics, indexing inspections, sitemaps, robots.txt lifecycle, redirects/DNS/HTTPS, CWV, log-based crawl stats, and persistent property notes. The notable gap is write operations on sitemaps (list/get only, no submit/delete) and no way to manage properties beyond reading them.