Yandex Webmaster MCP
Related Servers
Alternatives to Yandex Webmaster MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Yandex Metrica analytics: query web analytics metrics, goals, conversions, and raw API data using natural language from AI clients like Claude and Cursor.8708 npm5MIT
- 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
- AlicenseAqualityBmaintenanceThis 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.10125 npm4MIT
- AlicenseCqualityDmaintenanceMCP server that provides 46 tools for managing Yandex Webmaster API v4, enabling site management, sitemaps, indexing, search analytics, and more through natural language.4622 npm8MIT
- AlicenseAqualityCmaintenanceMCP server for interacting with Yandex.Webmaster API to manage sites, retrieve search queries, and check indexing status. Requires an OAuth token.1396 npm6MIT
- AlicenseAqualityBmaintenanceMCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.13114 npmMIT
TDQS
Scored across 20 tools
Most tools target clearly distinct resources and actions: auth lifecycle, site management, verification, diagnostics, query analytics, sitemaps, and links are well separated. Minor overlap exists between get_site_summary/get_site_diagnostics and between the history tools, and raw_request functionally overlaps every tool, but it is explicitly framed as a fallback for endpoints without dedicated tools.
Names follow a strong verb_noun snake_case convention (get_*, list_*, add_*, start_*, finish_*), which is readable and predictable. A few deviations (auth_status, logout, raw_request) are natural exceptions for lifecycle/utility operations rather than genuine inconsistency.
Twenty tools is on the heavier side but the domain is broad (auth, sites, verification, diagnostics, search analytics, sitemaps, links), and each tool maps to a distinct endpoint or workflow. No obvious filler tools, though a few read-heavy endpoints could have been consolidated.
Core workflows are covered: auth setup, site listing/adding, verification lifecycle, diagnostics, indexing history, recrawl requests, query analytics, and sitemap/link inspection. Missing operations such as deleting sites/sitemaps, sitemap detail, and recrawl quota/task status are acknowledged and reachable via raw_request, so they are workable gaps rather than dead ends.