Skip to main content
Glama
theYahia

Yandex Metrika MCP

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Yandex Metrika MCP

No user-submitted related servers found.

    Related Servers

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

      SvechaPVL
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for Yandex Direct, Metrika, Wordstat, and Webmaster APIs, providing 132 tools to manage advertising campaigns, analytics, keyword research, and reporting through any MCP-compatible client.
      59
      MIT

    • Yandex Webmaster MCP Server

      theYahia
      A
      license
      A
      quality
      C
      maintenance
      MCP server for interacting with Yandex.Webmaster API to manage sites, retrieve search queries, and check indexing status. Requires an OAuth token.
      13
      57 npm
      5
      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
      -

    • yandex-marketing-mcp

      skiddgoddamn
      A
      license
      B
      quality
      B
      maintenance
      MCP server for managing Yandex Direct advertising, Yandex Metrica analytics, Wordstat keyword research, and Yandex Webmaster SEO tools, with self-configuring OAuth; provides 153 tools for complete ad and search workflows from AI assistants.
      100
      19 npm
      2
      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

    A3.7/5.0

    Scored across 15 tools

    Disambiguation4/5

    Counter and goal tools are clearly separated by resource and action, and the specialized reporting tools have distinct intents. However, get_report is a flexible catch-all that overlaps with get_traffic_summary, get_traffic_sources, get_top_pages, get_report_comparison, and get_report_drilldown, which could cause misselection.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern: list_/create_/update_/delete_ for resource collections, and get_ for single entities or report views. The naming makes both resource type and action predictable across the whole toolset.

    Tool Count4/5

    15 tools is at the upper end of the ideal range, but the count is justified by the breadth of Yandex Metrika functionality: counter CRUD, goal management, log export, and multiple reporting variations. The reporting shortcuts add some redundancy but still map to concrete user needs.

    Completeness4/5

    Counter lifecycle is fully covered with create/read/update/delete, and reporting has broad query options with comparison, drilldown, and traffic summaries. The main gap is the missing update_goal operation, and export_logs only initiates/evaluates a log request without covering the full retrieval flow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources