seo-tools-mcp
Related Servers
Alternatives to seo-tools-mcp
No user-submitted related servers found.
Related Servers
- 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
- 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.7Apache 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
- AlicenseAqualityAmaintenanceMCP server for the Yandex Webmaster API, enabling natural-language queries about site indexing, search queries, IKS, diagnostics, sitemaps, and external links, as well as actions like recrawling, from AI assistants such as Claude, Cursor, and Codex.2021 npmMIT
- AlicenseAqualityBmaintenanceGoogle Search Console for Claude, Cursor & any MCP client — one sign-in, 30 seconds, no Google Cloud project. Six read-only tools (search analytics incl. Google Discover, period comparison with computed deltas, batch URL inspection, sitemaps) plus five built-in SEO analyses as slash-commands. Tokens stay on your machine. MIT.641 npm7MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP server that exposes Google Search Console tools (list sites, query analytics, inspect URL, list sitemaps) via natural language to AI assistants like ChatGPT and Claude.1MIT
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.