yandex-metrika-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| METRIKA_TOKEN | Yes | OAuth token with metrika:read and/or metrika:write permissions | |
| METRIKA_API_URL | No | API base URL (default: https://api-metrika.yandex.net) | https://api-metrika.yandex.net |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 68 tools
The tools are mostly distinguishable by resource/action naming (counters, goals, filters, segments, etc.), and the stat_* report variants target distinct report types. However, with 68 tools, an agent may hesitate between similar pairs such as stat_data vs stat_bytime or filter vs access_filter, so it is not a perfect 5.
The mgmt_<resource>_<action> pattern is used consistently across the management tools, and stat_* prefixes all report endpoints. Minor deviations like mgmt_counter_undelete, mgmt_cloud_export_remove, mgmt_accounts_update, and stat_data (noun-only) keep it from being fully uniform.
68 tools is far beyond the recommended 3-15 range and will make tool selection difficult for an agent, even though the underlying Yandex Metrika API is broad. This is too many for a coherent MCP surface.
The set covers the six main report variants and provides full CRUD-style coverage for most management resources, including counters, goals, filters, operations, grants, segments, and annotations. Minor gaps exist (e.g., no create/update for public grants or cloud exports, and no Logs API tools), but the main workflows are supported.