Developer · Local MCP server
Yandex Metrika
MCP server for Yandex Metrika API - counters, goals, reports, segments, logs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.dontsovcmc/yandex-metrika- Version
- 0.2.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-05-11
- Updated
- 2026-05-11
- Publisher
- dontsovcmc (GitHub) · 6 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/dontsovcmc) · how
- Repository
- github.com/dontsovcmc/mcp-server-yandex-metrika
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | mcp-server-yandex-metrika | 0.2.4 | stdio |
How to connect Yandex Metrika
Yandex Metrika runs locally from a Python package published to PyPI: mcp-server-yandex-metrika version 0.2.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx mcp-server-yandex-metrika. It reads the environment variable YANDEX_METRIKA_TOKEN (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"yandex-metrika": {
"command": "uvx",
"args": [
"mcp-server-yandex-metrika"
],
"env": {
"YANDEX_METRIKA_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from dontsovcmc (GitHub)
| Server | Runs |
|---|---|
| CdekMCP server for CDEK delivery service API - create orders, track shipments, search delivery points. | Local · stdio |
| Ozon SellerMCP server for Ozon Seller API - products, FBS/FBO, finance, analytics, returns. | Local · stdio |
| WildberriesMCP server for Wildberries Seller API - products, orders, supplies, analytics, advertising. | Local · stdio |
| Yandex DirectMCP server for Yandex Direct API v5 - campaigns, ads, keywords, bids, audiences. | Local · stdio |
| Yandex Market SellerMCP server for Yandex Market Partner API - orders, offers, prices, stocks, analytics. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| xytara MCP ExecutorPublic MCP server for summaries, DNS lookup, catalog, replies, and JSON checks. | Remote · HTTPLive check: ✓ handshake |
| YAACMessaging between concurrent AI coding sessions, across clients, over MCP. Zero infrastructure. | Local · stdio |
| Yaml Ai MCPAI-powered yaml ai MCP server for agents. Supports validate yaml, convert yaml json, lint yaml. By. | Local · stdio |
| Yandex Metrica MCPQuery Yandex Metrica analytics - reports, trends, metadata and raw log exports - via an AI agent. | Local · stdio |
| yandexgpt-mcpMCP server for YandexGPT - completions, embeddings, classification, summarization (Russia) | Local · stdio |
| YAP - Yet Another PackagerBuild native Linux packages (.deb/.rpm/.apk/.pkg.tar.zst) from a single PKGBUILD via MCP. | Local · stdio |
| YapitalismDrive terminal coding agents by voice, with receipts that never claim more than they proved. | Local · stdio |
| Yappy documentationYappy macOS docs (yappy.biz): setup, permissions, LLM backends, troubleshooting. | Remote · HTTPLive check: ✓ handshake |