Skip to main content
Glama
Sign In
yandex-metrica-mcp

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
      B
      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
      708 npm
      4
      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.
      157 npm
      MIT

    • Yandex Webmaster MCP

      askads
      A
      license
      A
      quality
      B
      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

    • metabase-mcp

      livingroot
      A
      license
      Not graded
      quality
      D
      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.
      68 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 has a distinct role: authentication, counter discovery/config, four reporting shapes, and the Logs API lifecycle. The reporting tools are clearly differentiated by output shape (flat rows, A/B comparison, tree drilldown, time series), and the metadata/counter-config split is explicitly cross-referenced.

    Naming Consistency4/5

    Most names follow predictable patterns within workflow groups: run_* for reports, logs_* for log-request lifecycle, and verb_noun for get_metadata, describe_counter, and submit_code. The lone outliers are login and the noun-prefixed logs_* group, but they remain readable and conventional.

    Tool Count5/5

    Twelve tools is well scoped for auth, discovery, reporting, and Logs API workflows. Each tool earns its place, with no obvious redundant variants or thin single-purpose surface.

    Completeness5/5

    The set covers the full practical lifecycle: sign-in with fallback, counter discovery and configuration, multiple report modalities, and log request/status/download/clean operations. No obvious dead ends are visible for the stated Yandex Metrica analytics purpose.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources