Skip to main content
Glama
Lermont

yadirect-mcp

by Lermont
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to yadirect-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
      -

    • AdsMCP

      skynes
      A
      license
      C
      quality
      C
      maintenance
      A local MCP server that unifies advertising campaigns, spend, and analytics from platforms such as Google Ads, Yandex Direct, Telegram Ads, and Microsoft Advertising into one interface for an AI agent, storing data locally in SQLite with explicit confirmation for external actions.
      143
      1
      MIT

    • Avito Ads MCP

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      MCP server that enables natural-language interaction with the Avito Ads advertising API, including campaign, ad group, and creative management, statistics retrieval, fund transfers, and ORD paperwork filing.
      26
      31 npm
      1
      MIT

    • 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
      6 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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource or stage: clients, campaigns, wordstat, regions, account settings, ads, report export, and report reading. report and read_report are clearly separated as fetch vs read saved output, so there is no real overlap.

    Naming Consistency4/5

    All tools share the direct_ prefix and use snake_case, making the family identifiable. Most are direct_<noun> (direct_campaigns, direct_ads), while direct_list_clients and direct_read_report use verb_noun, a minor but visible deviation.

    Tool Count5/5

    Eight tools is a well-scoped count for a Yandex Direct analysis/read-only API surface. Each tool addresses a distinct need without redundancy or bloat.

    Completeness4/5

    The set covers the main read/analysis workflows: client selection, campaign/ads/settings inspection, wordstat and region lookups, plus report generation and paginated reading. Minor gaps exist—no goal-list retrieval or management operations—but the core analytical workflow is not dead-ended.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources