Skip to main content
Glama
askads

Yandex Webmaster MCP

Related Servers

Alternatives to Yandex Webmaster MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      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
      67 npm
      2
      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
      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
      44 npm
      3
      MIT
    • 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
      13 npm
      5
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for interacting with Yandex.Webmaster API to manage sites, retrieve search queries, and check indexing status. Requires an OAuth token.
      13
      61 npm
      4
      MIT
    • A
      license
      A
      quality
      A
      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
      70 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 20 tools

    Disambiguation4/5

    Tools are mostly distinct, targeting specific actions (add, start_verification, get_verification_status) or distinct resources (sites, diagnostics, queries). However, get_site_summary and get_site_diagnostics both report site problems, and get_popular_queries vs get_search_queries_history have overlapping query data.

    Naming Consistency4/5

    Names follow a clear verb_noun pattern (add_site, get_site_summary, list_sites, start_verification). Minor deviations like raw_request and auth_status are acceptable, but most tools are consistent.

    Tool Count4/5

    20 tools is on the higher end but justified for the broad domain (auth, sites, verification, diagnostics, analytics, sitemaps, external links). The count is slightly heavy but not excessive for a full API wrapper.

    Completeness4/5

    The surface covers core workflows: site management, verification, diagnostics, analytics, sitemaps, recrawl. Minor gaps exist (e.g., no update/delete site except via raw_request), but the raw_request fallback and clear lifecycle coverage make it mostly complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues