yandex-metrica-mcp
Related Servers
Alternatives to yandex-metrica-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Yandex.Metrica API providing 15 tools for managing counters, goals, reports, logs, traffic sources, and top pages with OAuth Bearer token authentication.1582 npm1MIT
- AlicenseNot gradedqualityFmaintenanceMCP 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.58MIT
- AlicenseAqualityDmaintenanceMCP server for Yandex Metrika API, enabling reporting, counter management, goals, filters, and other operations via natural language.122MIT
- AlicenseCqualityAmaintenanceEnables interaction with Yandex Metrika's Reports and Management APIs, providing tools for querying analytics data and managing counters, goals, filters, and other settings.68MIT
- AlicenseAqualityBmaintenanceEnables safe, informed management of Yandex.Direct accounts through 11 MCP tools, covering reads, planned two-phase writes, reports, media attachment, Wordstat, Metrika, and Audience operations, while exposing platform knowledge as resources such as limits, traps, and the red line of deliberately absent destructive actions.11MIT
- FlicenseNot gradedqualityDmaintenanceA 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-
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose, with explicit cross-references in descriptions (e.g., 'Do not use this... call X instead') that prevent misselection. The split between aggregated reports, logs export lifecycle, and counter management is unambiguous.
All tools follow a consistent yandex_metrica_ prefix and verb_noun pattern (list_counters, get_counter, create_logs_request, download_logs_part, etc.). No mixing of conventions or styles.
13 tools is well within the ideal 3-15 range and each tool maps to a distinct API operation or step in a workflow. The logs export lifecycle is fully broken out without redundancy.
Core workflows (counter listing/retrieval/creation/deletion, reporting, full logs export lifecycle) are covered. Minor gaps exist, such as no counter update/settings modification and only goal listing without goal management, but these are not critical for typical agent tasks.