Skip to main content
Glama
BoxLab-Ltd

yandex-metrica-mcp

by BoxLab-Ltd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to yandex-metrica-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
      75 npm
      3
      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.
      63 npm
      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
      99 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

    • metabase-mcp

      livingroot
      A
      license
      Not graded
      quality
      C
      maintenance
      A TypeScript/Node.js MCP server that wraps the Metabase REST API, enabling AI agents to execute queries, explore schemas, and build dashboards through structured tool calls.
      66 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.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct action: auth (login, submit_code), metadata discovery (get_metadata, describe_counter), reporting variations (run_report, run_comparison, run_drilldown, run_timeseries), and Logs API lifecycle (logs_request, logs_status, logs_download, logs_clean). The run_* and logs_* groups are clearly differentiated by their descriptions, and get_metadata is explicitly distinct from describe_counter for listing vs. single counter config.

    Naming Consistency5/5

    Tool names follow a consistent lowercase snake_case convention with predictable prefixes: run_* for report types, logs_* for Logs API operations, and descriptive verb_noun names like get_metadata and describe_counter. Login and submit_code are also verb-focused and fit the pattern. The naming is uniform and intuitive.

    Tool Count5/5

    12 tools is well-scoped for a Metrica MCP covering authentication, metadata, four reporting modes, and the complete Logs API cycle (request, status, download, clean). Each tool has a clear purpose and the count is within the ideal 3-15 range, with no redundancy.

    Completeness5/5

    The tool surface covers the full workflow: sign-in, discover counters and fields, run standard/comparison/drilldown/timeseries reports, and for raw data: create, poll, download, and clean Logs API requests. There are no dead ends—logs_download requires processed status, logs_clean handles both finished and in-progress requests, and metadata tools guide users to valid fields. The domain is fully addressed for read-heavy analytics.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources