Skip to main content
Glama
askads

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
      102 npm
      13
      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
      55 npm
      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
      C
      maintenance
      Read-only MCP server for Yandex Metrika analytics, enabling report retrieval via MCP clients like Claude Code or Cursor without modifying any data.
      47 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.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: auth status, login/logout flow, listing counters/goals, fetching statistics, and a generic raw request. No two tools overlap in purpose, and even similar operations (list_goals vs list_counters) are clearly differentiated by resource type.

    Naming Consistency4/5

    The naming is predominantly verb_noun in lowercase snake_case (list_goals, get_statistics, start_login, finish_login). Minor deviations: 'auth_status' and 'logout' are not strictly verb_noun, but they follow the same case style and are idiomatic for their actions. The overall pattern is consistent.

    Tool Count5/5

    Eight tools is a well‑scoped set for a Yandex Metrica MCP server. It covers authentication (3 tools), resource listing (3 tools), statistics (1 tool), and a flexible raw API access (1 tool) without being bloated or insufficient.

    Completeness5/5

    The tool set comprehensively addresses the core Yandex Metrica workflows: authentication, listing counters and goals, retrieving statistics, and raw access to any API endpoint. The inclusion of raw_request fills any gaps for operations not covered by dedicated tools, ensuring no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources