Skip to main content
Glama
gmen1057

yandex-direct-mcp

by gmen1057
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to yandex-direct-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • yandex-direct-mcp

      theYahia
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Yandex.Direct API v5 enabling management of campaigns, ad groups, ads, keywords, statistics, and account info via 12 tools.
      20
      102 npm
      5
      MIT

    • yandex-direct-mcp

      nikolaymokh-dev
      A
      license
      B
      quality
      C
      maintenance
      A hardened MCP server for managing Yandex.Direct advertising campaigns with read-only defaults, write and finance capabilities optional, using OAuth authentication.
      26
      MIT

    • 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
      10 npm
      3
      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
    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

    B3.2/5.0

    Scored across 80 tools

    Disambiguation3/5

    Most tools have distinct targets, but the many budget/strategy write tools (set_max_conv, set_strategy, set_daily_budget, set_network_weekly_budget, set_search_weekly_budget) overlap in purpose and could confuse an agent. Some list/get tools are also similar, though descriptions help.

    Naming Consistency4/5

    The vast majority follow direct_verb_noun (e.g., list_campaigns, set_keyword_bids, delete_keywords). A few anomalies like direct_ping, direct_rpc, direct_account_summary, and direct_client_info deviate from the verb-first pattern, but the overall convention is clear and predictable.

    Tool Count1/5

    With 80 tools, the server is far beyond the typical well-scoped range. Even for a complex API, this number is excessive and will likely overwhelm agents, making tool selection harder rather than easier.

    Completeness5/5

    The tool set covers the full lifecycle of Yandex Direct campaigns: creation, management, bidding, budgets, extensions, reporting, and even a raw RPC escape hatch. There are no obvious dead ends; nearly every operation an agent could need is present.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources