seo-tools-mcp
Related Servers
Alternatives to seo-tools-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP servers for Yandex APIs: Search, Wordstat, Webmaster, Metrika, Direct. 94 tools, Claude Code plugin included.3319MIT
- AlicenseBqualityCmaintenanceA production-oriented, read-only Google Search Console MCP server and TypeScript SDK for Claude, Cursor, VS Code, and other MCP clients. Query real Search Console data, inspect indexed URLs, review sitemaps, compare periods, and surface transparent SEO opportunities without handing private data to a third-party SaaS.20MIT
- AlicenseNot gradedqualityCmaintenanceSelf-hosted Google Search Console MCP server that lets ChatGPT, Claude, or other MCP clients query GSC data in natural language. It exposes tools to list sites, query Search Analytics, inspect URLs, and list sitemaps.MIT
- AlicenseAqualityCmaintenanceMCP server for querying Google Search Console data — search analytics, URL inspection, sitemap monitoring, and more — read-only tools for any MCP-compatible AI client.764 PyPIApache 2.0
- AlicenseAqualityDmaintenanceLocal-first MCP server for Yandex Webmaster that exposes tools for SEO operations including search query analytics, sitemap management, indexing history, recrawl quota, and diagnostics.15MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude, Cursor, VS Code, ChatGPT and other MCP clients to analyze Google Search Console, Google Ads and AdSense data through 57 read-only tools covering search performance, indexing, wasted ad spend, quality scores, earnings and combined paid-vs-organic insights. Runs as a thin local client against a hosted backend, so no Google Cloud project, OAuth client or developer token is needed.456 npmMIT
TDQS
Scored across 11 tools
Tools are generally distinct: search types, wordstat variants, and auth/balance are clearly separated. However, xmlstock_wordstat_regions and xmlstock_wordstat_regions_tree share a very similar prefix and could cause initial confusion, though their descriptions resolve the ambiguity.
All tools share the xmlstock_ prefix and use snake_case, which is consistent. Some names are nouns (xmlstock_serp, xmlstock_images) while others use verbs (xmlstock_set_credentials), creating a minor stylistic deviation but no major inconsistency.
11 tools is well within the ideal range and each tool covers a meaningful XMLStock feature: auth, credentials, balance, SERP, three vertical searches, and a complete Wordstat suite. No tool feels redundant or unnecessary.
The tool surface fully covers the XMLStock SEO API scope: setup and validation, balance monitoring, web/image/news/video search, and wordstat frequency, dynamics, regional distribution, and region tree. No critical workflow dead ends are apparent.