Skip to main content
Glama
stufently

Yandex MCP

by stufently
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Yandex MCP

No user-submitted related servers found.

    Related Servers

    • yandex-mcp

      zai-one
      F
      license
      C
      quality
      A
      maintenance
      MCP server for Yandex Direct, Metrika, Search API, Wordstat and Webmaster. Connect an AI assistant to advertising, website analytics, search results and search-demand data.
      127
      1
      -

    • yandex-marketing-mcp

      skiddgoddamn
      A
      license
      B
      quality
      C
      maintenance
      MCP server for managing Yandex Direct advertising, Yandex Metrica analytics, Wordstat keyword research, and Yandex Webmaster SEO tools, with self-configuring OAuth; provides 153 tools for complete ad and search workflows from AI assistants.
      100
      13 npm
      3
      MIT

    • Yandex Webmaster MCP

      askads
      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
      93 npm
      MIT

    • Yandex Wordstat MCP

      N1arko
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for querying Yandex Wordstat via Yandex Cloud Search API. Enables checking phrase frequency, similar queries, regional demand, and seasonality trends.
      1
      MIT

    • yandex-mcp

      SvechaPVL
      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.
      58
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 33 tools

    Disambiguation4/5

    Descriptions are unusually explicit with 'Do not use' cross-references, which strongly mitigates confusion. However, the set contains many near-identical history/sample/event tools (e.g., get-indexing-history vs get-insearch-history vs get-search-events-history; get-excluded-pages vs get-search-events-samples) that still require careful reading, so some misselection risk remains.

    Naming Consistency5/5

    All tool names use consistent kebab-case verb_noun patterns: get-*, add-*, list-*, delete-*, start-*, verify-host. The only minor variation is verify-host vs start-verification, but both are predictable and readable.

    Tool Count2/5

    With 33 tools, the server exceeds the 25+ heavy threshold. While Yandex Webmaster is a broad domain, the many read-only history/sample variants inflate the surface beyond what most agents need in a single call, making the set feel over-scoped.

    Completeness4/5

    The surface covers host lifecycle, verification, sitemaps, recrawl, important URLs, indexing/search/events, external links, and broken internal links. Some gaps remain (e.g., sitemap deletion, important-URL mutations), but core workflows are well supported.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources