Yandex Webmaster MCP Server
Related Servers
Alternatives to Yandex Webmaster MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceThis MCP server lets you query Yandex Webmaster data in plain language, covering search queries, indexing, diagnostics, sitemaps, backlinks, and recrawl status. It is read-only by default (except recrawl submission) and uses OAuth without storing secrets.1044 npm3MIT
- 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.2099 npmMIT
- AlicenseCqualityCmaintenanceMCP server that provides 46 tools for managing Yandex Webmaster API v4, enabling site management, sitemaps, indexing, search analytics, and more through natural language.4611 npm6MIT
- AlicenseAqualityCmaintenanceMCP server for Yandex.Metrica API providing 15 tools for managing counters, goals, reports, logs, traffic sources, and top pages with OAuth Bearer token authentication.1546 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for Yandex Metrika API, enabling reporting, counter management, goals, filters, and other operations via natural language.122MIT
TDQS
Scored across 13 tools
Most tools have distinct purposes (e.g., get_hosts lists sites, get_query_analytics aggregates time series), but get_popular_search_queries and get_search_queries overlap, with one explicitly deprecated. The descriptions clarify the distinction, so misselection is unlikely.
All tools follow a consistent 'get_' prefix with descriptive nouns, except submit_url which is a clear action verb. The pattern is uniform and readable, with no mixed conventions.
13 tools is a well-scoped size for a Yandex Webmaster server, covering diagnostics, analytics, indexing, and recrawl without being overwhelming or too sparse.
The surface covers core domain needs: diagnostics, analytics, indexing, sitemaps, and recrawl submission. Minor gaps exist (e.g., no verification or sitemap submission), but most workflows are supported. The deprecated get_search_queries slightly clutters the set.