Skip to main content
Glama
A1-x-Tech

Yandex Audience MCP

by A1-x-Tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Yandex Audience MCP

No user-submitted related servers found.

    Related Servers

    • 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
      96 npm
      2
      MIT

    • io.github.dontsovcmc/yandex

      dontsovcmc
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Yandex Metrika API, enabling reporting, counter management, goals, filters, and other operations via natural language.
      12
      2
      MIT

    • Yandex Merchants MCP

      A1-x-Tech
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Merchants API enabling management of product offers (prices, discounts, hide/show) via natural language from AI assistants like Claude and Cursor.
      13
      89 npm
      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
      200 npm
      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.3/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: pixels, segments, segment grants, authentication, and raw API access are cleanly separated. Even the two upload tools are clearly differentiated by file format (TSV/TXT versus CSV CRM) and by the confirm_segment follow-up step.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern: create_pixel, delete_segment, list_segments, add_segment_grant. Minor exceptions like auth_status, logout, and raw_request break the pattern slightly, but they are still readable and predictable in context.

    Tool Count4/5

    Twenty tools is on the higher end, but the count is justified by the breadth of the Yandex Audience API: pixels, segments, grants, auth lifecycle, and an escape hatch. There is little redundancy and each tool appears to earn its place, so it feels slightly broad rather than bloated.

    Completeness5/5

    The tool set covers the full lifecycle for pixels, segments, and grants, plus authentication and a raw_request fallback for rarely used API operations. There are no obvious dead ends: file uploads have a confirm step, lookalike and pixel segments have creation paths, and missing operations like reprocess or undelete are accessible through raw_request.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources