Skip to main content
Glama
zai-one

yandex-mcp

by zai-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to yandex-mcp

No user-submitted related servers found.

    Related Servers

    • yandex-marketing-mcp

      skiddgoddamn
      A
      license
      B
      quality
      B
      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
      19 npm
      2
      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.
      59
      MIT

    • yadirect-mcp

      Lermont
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that connects Yandex Direct advertising reports and safe campaign creation to AI agents, enabling natural-language analytics and protected campaign setup.
      8
      2
      MIT

    • Yandex Metrica MCP

      askads
      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
      103 npm
      4
      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

    C2.9/5.0

    Scored across 48 tools

    Disambiguation3/5

    Most tools map to distinct resource-action pairs, and product prefixes help separate Wordstat, SERP, Direct, Metrika, and Webmaster. However, several read/report tools overlap in function (metrika_report vs metrika_get_statistics, direct_get_campaign vs direct_get_inventory, webmaster_get_sitemap vs list_sitemaps vs list_user_sitemaps), requiring careful description reading to avoid misselection.

    Naming Consistency4/5

    Tool names are mostly consistent within each product area, following a service-specific prefix plus verb_noun pattern (e.g., direct_list_campaigns, metrika_list_counters, webmaster_get_diagnostics). Some deviations exist, such as yandex_wordstat_regions and yandex_wordstat_dynamics lacking a verb, so the pattern is not perfectly uniform.

    Tool Count2/5

    With 48 tools, the server is heavily overloaded for a single MCP surface, far exceeding the typical 3-15 well-scoped range. Although the tools are grouped by Yandex product, the sheer number of near-repetitive Webmaster read endpoints makes the set feel bloated and harder for an agent to navigate efficiently.

    Completeness4/5

    The tool set covers the major Yandex product areas comprehensively: Wordstat research, SERP async workflow, Direct campaign management and writes, Metrika statistics/goals, and extensive Webmaster read/reconcile/apply operations. Minor gaps exist, such as no explicit verification-start tool or no direct counter creation, but agents can accomplish core workflows with the available surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources