Skip to main content
Glama
dontsovcmc

io.github.dontsovcmc/yandex-metrika

by dontsovcmc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to io.github.dontsovcmc/yandex-metrika

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

      theYahia
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Yandex.Metrica API providing 15 tools for managing counters, goals, reports, logs, traffic sources, and top pages with OAuth Bearer token authentication.
      15
      46 npm
      1
      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-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
      -
    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.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search for actions, execute them, list specific resources (labels, counters, goals, etc.), and generate reports. There is no ambiguity between tools, and even similar report tools are differentiated by type.

    Naming Consistency5/5

    All tools follow the 'ym_<resource_or_action>' pattern consistently. Names are descriptive and predictable, with only minor internal underscores (e.g., stat_data) which do not break the pattern.

    Tool Count5/5

    12 tools is well-scoped for a Yandex Metrika server. It covers core resources (counters, goals, segments, etc.) and adds generic search/execute for extensibility without bloat.

    Completeness5/5

    The tool set covers all major Metrika operations with dedicated tools (counters, stats, goals, etc.) and provides a generic ym_execute for any remaining actions. This hybrid approach leaves no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources