SEO Webmaster MCP
Related Servers
Alternatives to SEO Webmaster MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run SEO audits and reporting over a user's own Search Console, Google Analytics, Bing, and keyword/competitor provider data, including page/index status, traffic comparisons, backlinks, and local crawl/internal-link analysis.4,336 npm613Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to perform evidence-backed Google Search Console investigations, including traffic change diagnosis, opportunity discovery, cannibalization detection, and indexing audits, all through read-only access.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to research competitors, keywords, ads, and AI citations, and to audit public websites for SEO, AEO, and GEO readiness with prioritized fixes.MIT
- AlicenseNot gradedqualityDmaintenanceAudits public websites for AI crawler access, public technical signals, and deployment readiness. Includes a focused path to the full readiness report when deeper remediation guidance is needed.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to query Google Search Console search performance, inspect indexing, analyze sitemaps, and run SEO analyses such as cannibalisation detection, query clustering, and wins/losses, all with read-only access.20119 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables auditing AI search visibility: checks site readiness for AI crawlers and measures whether ChatGPT, Gemini, and Perplexity recommend your site, including verbatim answers and citation gap analysis.90 npm4AGPL 3.0
TDQS
Scored across 29 tools
The bing_/gsc_ provider prefixes cleanly separate most tools, but several pairs overlap: gsc_search_performance vs gsc_query_advanced vs gsc_page_performance all query Search Analytics, and seo_audit_site vs seo_audit_advanced vs seo_audit_save all perform audits with only subtle differences. Descriptions do the heavy lifting to distinguish them, so an agent can recover but selection errors are likely. Also bing_portal_tools and geo_report_summary feel like odd out-of-band additions to an otherwise analytical set.
A clear prefix_action convention (bing_*, gsc_*, seo_audit_*) holds across 25 of 29 tools. Violations are minor: get_bing_clicks_and_impressions uses a get_ verb instead of the bing_ prefix, and geo_report_summary is unprefixed.
29 tools is heavy, but justified in part by covering two separate provider APIs (Bing + GSC) plus an audit lifecycle. Some entries feel marginal: bing_portal_tools merely returns documentation links, geo_report_summary reads a local CSV, and bing_top_pages/bing_top_queries/bing_page_queries overlap.
Coverage is broad: analytics, sitemaps, crawl stats, backlinks, URL inspection, opportunities, and a full audit run/save/list/get/compare lifecycle. Notable gaps: no sitemap submission or URL indexing request for either Bing or GSC, all provider tools are read-only, and geo_report_summary has no sibling tools for managing the CSVs.