Skip to main content
Glama
Crash-SV

Yandex Webmaster MCP Server

by Crash-SV

Related Servers

Alternatives to Yandex Webmaster MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      C
      maintenance
      MCP server that provides 46 tools for managing Yandex Webmaster API v4, enabling site management, sitemaps, indexing, search analytics, and more through natural language.
      46
      24 npm
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with Yandex.Webmaster API to manage sites, retrieve search queries, and check indexing status. Requires an OAuth token.
      13
      72 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for Yandex Direct, Metrika, Wordstat, and Webmaster APIs, providing 132 tools to manage advertising campaigns, analytics, keyword research, and reporting through any MCP-compatible client.
      59
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Local-first MCP server for Yandex Webmaster that exposes tools for SEO operations including search query analytics, sitemap management, indexing history, recrawl quota, and diagnostics.
      15
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP 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.
      20
      99 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      This 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.
      10
      80 npm
      3
      MIT

    TDQS

    B3/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools target distinct resources and actions clearly (recrawl, indexing, search URLs, queries, sitemaps). A few clusters risk confusion: get_sitemap_info vs get_user_added_sitemap_info, get_sitemaps vs get_user_added_sitemaps, and get_hosts vs get_host_info, but the descriptions differentiate them.

    Naming Consistency4/5

    Consistent snake_case verb_noun pattern throughout (add_host, get_host_info, delete_sitemap, request_recrawl). Minor deviations like get_X_info/get_X_history/get_X_samples layering and verbs add/get/delete/verify/request are predictable and readable.

    Tool Count3/5

    37 tools is on the heavy side, mapping to broad coverage of a large API domain. Each tool roughly earns its place, but the count is high enough to burden selection and could be consolidated (e.g. sitemap and search-URL variants).

    Completeness4/5

    Strong lifecycle coverage across hosts, sitemaps, recrawl, indexing, queries, diagnostics, and links, with both history and sample endpoints. Some gaps remain (e.g. update/modify operations for monitored URLs), but core workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues