MCP server for Yandex Metrika API — counters, goals, reports, segments, logs
MCP server for Yandex Metrika API — counters, goals, reports, segments, logs. Exposed over MCP by the yandex mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
claude mcp add yandex-metrika \ -e YANDEX_METRIKA_TOKEN=ваш_токен \ -- mcp-server-yandex-metrika ```
mcp-server-yandex-metrika on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
ym_stat_data — stat-dataym_stat_data_bytime — stat-bytimeym_stat_data_drilldown — stat-drilldownym_stat_data_comparison — stat-comparisonym_stat_data_comparison_drilldown — —ym_log_requests — log-requestsym_log_request — —ym_log_request_create — log-request-createym_log_request_evaluate — log-request-evaluateym_log_request_clean — —ym_log_request_cancel — —ym_log_request_download — log-downloadYou will need one environment variable: YANDEX_METRIKA_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Yandex's toolset — ym_stat_data, ym_stat_data_bytime, ym_stat_data_drilldown and 9 more — is a fair guide to whether it matches your workflow. It is maintained by dontsovcmc; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| ym_stat_data | stat-data |
| ym_stat_data_bytime | stat-bytime |
| ym_stat_data_drilldown | stat-drilldown |
| ym_stat_data_comparison | stat-comparison |
| ym_stat_data_comparison_drilldown | — |
| ym_log_requests | log-requests |
| ym_log_request | — |
| ym_log_request_create | log-request-create |
| ym_log_request_evaluate | log-request-evaluate |
| ym_log_request_clean | — |
| ym_log_request_cancel | — |
| ym_log_request_download | log-download |
{
"mcpServers": {
"yandex-metrika": {
"command": "uvx",
"args": ["mcp-server-yandex-metrika"],
"env": {
"YANDEX_METRIKA_TOKEN": "ваш_токен"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YANDEX_METRIKA_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.