Skip to main content
Glama
Yandex Webmaster MCP

Yandex Webmaster MCP

Related Servers

Alternatives to Yandex Webmaster MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      8
      708 npm
      5
      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
      B
      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
      125 npm
      4
      MIT
    • A
      license
      C
      quality
      D
      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
      22 npm
      8
      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
      96 npm
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.
      13
      114 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues