Skip to main content
Glama
Rezlazy

yandex-metrika-mcp

by Rezlazy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to yandex-metrika-mcp

No user-submitted related servers found.

    Related Servers

    • yandex-metrika-mcp

      IlyaVorozhbit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to retrieve comprehensive analytics data from Yandex Metrika accounts, including traffic, content, e-commerce, and user demographics.
      69 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 Metrika MCP

      Vadosdavos
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides access to Yandex Metrika analytics data through various tools and functions. This server allows AI assistants and applications to retrieve comprehensive analytics data from Yandex Metrika accounts.
      1
      -

    • Yandex Direct MCP

      askads
      A
      license
      B
      quality
      A
      maintenance
      Enables managing Yandex Direct PPC campaigns, ad groups, ads, and keywords, plus pulling performance statistics via the Yandex Direct API v5.
      44
      124 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
    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

    C2.7/5.0

    Scored across 68 tools

    Disambiguation4/5

    The tools are mostly distinguishable by resource/action naming (counters, goals, filters, segments, etc.), and the stat_* report variants target distinct report types. However, with 68 tools, an agent may hesitate between similar pairs such as stat_data vs stat_bytime or filter vs access_filter, so it is not a perfect 5.

    Naming Consistency4/5

    The mgmt_<resource>_<action> pattern is used consistently across the management tools, and stat_* prefixes all report endpoints. Minor deviations like mgmt_counter_undelete, mgmt_cloud_export_remove, mgmt_accounts_update, and stat_data (noun-only) keep it from being fully uniform.

    Tool Count2/5

    68 tools is far beyond the recommended 3-15 range and will make tool selection difficult for an agent, even though the underlying Yandex Metrika API is broad. This is too many for a coherent MCP surface.

    Completeness4/5

    The set covers the six main report variants and provides full CRUD-style coverage for most management resources, including counters, goals, filters, operations, grants, segments, and annotations. Minor gaps exist (e.g., no create/update for public grants or cloud exports, and no Logs API tools), but the main workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources