Skip to main content
Glama
Sign In
Yandex Metrica MCP

Yandex Metrica MCP

by askads
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Yandex Metrica MCP

No user-submitted related servers found.

    Related Servers

    • yandex-metrica-mcp

      BoxLab-Ltd
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Metrica — query your web analytics in plain language from Claude, Cursor, and other AI agents. Secretless one-command login (PKCE), read-only, TypeScript.
      12
      223 npm
      15
      MIT

    • Yandex Webmaster MCP

      askads
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the Yandex Webmaster API, enabling natural-language queries about site indexing, search queries, IKS, diagnostics, sitemaps, and external links, as well as actions like recrawling, from AI assistants such as Claude, Cursor, and Codex.
      20
      1,334 npm
      1
      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-metrika-mcp

      nikolaymokh-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for Yandex Metrika analytics, enabling report retrieval via MCP clients like Claude Code or Cursor without modifying any data.
      609 npm
      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
      -
    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

    Disambiguation4/5

    Each tool has a distinct role: counter listing, goal listing, statistics querying, auth lifecycle steps (auth_status/start_login/finish_login/logout), and a generic escape hatch. The only real overlap is raw_request, which can reach the same endpoints as list_counters/list_goals/get_statistics, but it is explicitly framed as a fallback for uncovered endpoints. Minor risk that an agent picks raw_request when a purpose-built tool exists.

    Naming Consistency4/5

    Most names follow a verb_noun pattern (list_counters, list_goals, get_statistics, start_login, finish_login) with logout and raw_request as single-verb/noun forms. auth_status is a noun phrase that breaks the pattern slightly. Overall predictable and readable, with no camelCase/snake_case mixing.

    Tool Count5/5

    Eight tools is well within the healthy range and each maps to a real need: two read tools, two supporting lookup tools, four auth lifecycle tools, and one escape hatch. Nothing feels padded or thin for a read-oriented Metrica integration.

    Completeness4/5

    The core workflow (list counters -> list goals -> query statistics) is fully covered, plus a complete token login/logout lifecycle. Write operations (creating counters, editing goals) and less common endpoints are only reachable via raw_request, which is a workable but not first-class gap.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources