Skip to main content
Glama
nikolaymokh-dev

yandex-direct-mcp

by nikolaymokh-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to yandex-direct-mcp

No user-submitted related servers found.

    Related Servers

    • yandex-direct-mcp

      gmen1057
      A
      license
      B
      quality
      C
      maintenance
      An MCP server for Yandex Direct advertising API, providing ~80 tools to view and modify campaigns, keywords, budgets, and stats with safe write access.
      80
      16 npm
      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-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-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
    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 26 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, grouped by functional area (auth, changes, dictionaries, keywordsresearch, leads, reports, v4*). Within groups, create/get/list patterns are well-separated, and descriptions clarify any potential overlap.

    Naming Consistency5/5

    Tool names follow a consistent area_verb pattern (e.g., auth_login, dictionaries_get, v4forecast_create). The only exception is tool_help, a meta tool. All others adhere to snake_case and predictable naming.

    Tool Count4/5

    26 tools is slightly above the typical 3-15 range, but it is justified by the breadth of features covered (authentication, changes, dictionaries, keyword research, leads, reporting, v4 Live API). The organization keeps it manageable.

    Completeness2/5

    The tool set focuses on data retrieval and analysis (reports, dictionaries, changes, forecasts) but lacks core campaign management operations such as creating, updating, or deleting campaigns, ad groups, or bids. This limits its completeness for full Yandex Direct management.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources