Skip to main content
Glama
mrkhachaturov

ya-metrics-mcp

by mrkhachaturov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ya-metrics-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
      67 npm
      2
      MIT

    • yandex-mcp

      zai-one
      F
      license
      C
      quality
      A
      maintenance
      MCP server for Yandex Direct, Metrika, Search API, Wordstat and Webmaster. Connect an AI assistant to advertising, website analytics, search results and search-demand data.
      48
      1
      -

    • 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
      -

    • 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

    • yadirect-mcp

      Lermont
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that connects Yandex Direct advertising reports and safe campaign creation to AI agents, enabling natural-language analytics and protected campaign setup.
      8
      2
      MIT

    • appmetrica-mcp

      pavellunev
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Yandex AppMetrica analytics, enabling Claude to access reports, raw event logs, crash data, and push notification campaigns.
      11
      7 npm
      3
      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.9/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists (e.g., get_browsers_report vs get_device_analysis both deal with browser information). Descriptions generally help differentiate them.

    Naming Consistency3/5

    Naming is mixed: most tools use get_<noun>, but there are list_ and compare_ prefixes, and anomalies like sources_search_phrases. The pattern is inconsistent but still readable.

    Tool Count2/5

    With 31 tools, the surface is too large for a focused analytics server. Many tools are granular, increasing risk of agent misselection and making the tool set feel bloated.

    Completeness4/5

    Core analytics areas are well-covered: traffic sources, content, e-commerce, goals, devices, geography. Minor gaps exist (e.g., no funnel or path analysis), but the set is largely complete for standard reporting.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources