Skip to main content
Glama
askads

Yandex Direct MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Yandex Direct MCP

No user-submitted related servers found.

    Related Servers

    • yandex-direct

      dontsovcmc
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Yandex Direct advertising campaigns, ads, keywords, and reports via natural language using the Yandex Direct API v5.
      2
      1
      MIT

    • yandex-direct-mcp

      iarbor04
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage Yandex Direct advertising accounts via the API v5, including reports, bids, campaign management, and semantic analysis through natural language requests.
      4
      16 npm
      MIT

    • yandex-direct-mcp-plus

      Pavelsiba
      A
      license
      C
      quality
      A
      maintenance
      Enables managing Yandex.Direct contextual advertising campaigns directly from an MCP client chat, covering campaigns, ad groups, ads and moderation, keywords and bids, negative keywords, bid adjustments, retargeting, feeds, statistics, search queries, and account balance. All monetary values are handled in rubles and 64-bit IDs are kept as strings to avoid precision loss.
      60
      547 npm
      1
      MIT

    • Yandex MCP Server

      mlenkov
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with Yandex advertising and analytics APIs (Direct, Metrika, Audience, Webmaster, AdMetrica) through MCP tools, resources, and prompts for campaign management and data retrieval.
      MIT

    • yandex-direct-mcp

      artgas1
      A
      license
      A
      quality
      A
      maintenance
      Enables natural language interaction with Yandex Direct API v5 via MCP, providing 113 generated methods with accurate handling of monetary amounts and 64-bit IDs, plus a command-line mode.
      13
      627 npm
      1
      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.4/5.0

    Scored across 44 tools

    Disambiguation4/5

    Most tools target a distinct resource/action pair: campaigns, ad groups, ads, keywords, bid modifiers, and extension libraries. The only real ambiguity is between add_bid_modifier and set_bid_modifiers or between the various extension create/add tools, but the descriptions and resource nouns keep boundaries mostly clear.

    Naming Consistency3/5

    The set mostly follows a verb_noun snake_case pattern, but there are notable inconsistencies: create_vcard vs delete_vcards, create_sitelinks_set vs get_sitelinks/delete_sitelinks, and a mix of add_ and create_ for similar creation operations. Non-verb names like logout, auth_status, and raw_request further weaken the pattern.

    Tool Count2/5

    44 tools is far above a well-scoped surface, and many are thin CRUD wrappers for extension libraries and media that could have been consolidated. The presence of raw_request as an arbitrary API fallback makes the large number of dedicated wrappers feel inflated.

    Completeness2/5

    Core CRUD for campaigns, ad groups, ads, keywords, and bid modifiers is covered, along with auth and reporting. However, there is no dedicated way to attach callouts, sitelinks, or vcards to ads, no image field on text ad create/update, and only text campaign/ad types are wrapped, leaving common workflows to raw_request.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources