Developer · Local MCP server
Yandex Metrica MCP
Query Yandex Metrica analytics - reports, trends, metadata and raw log exports - via an AI agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.BoxLab-Ltd/yandex-metrica-mcp- Version
- 0.3.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-21
- Updated
- 2026-07-21
- Publisher
- BoxLab-Ltd (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/BoxLab-Ltd) · how
- Repository
- github.com/BoxLab-Ltd/yandex-metrica-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | yandex-metrica-mcp | 0.3.0 | stdio |
How to connect Yandex Metrica MCP
Yandex Metrica MCP runs locally from a Node.js package published to the npm registry: yandex-metrica-mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y yandex-metrica-mcp@0.3.0. It reads these environment variables: YANDEX_METRIKA_TOKEN (secret), YANDEX_METRIKA_COUNTER_ID and YANDEX_METRIKA_LOGS_DIR; set them 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-metrica-mcp": {
"command": "npx",
"args": [
"-y",
"yandex-metrica-mcp@0.3.0"
],
"env": {
"YANDEX_METRIKA_TOKEN": "<secret>",
"YANDEX_METRIKA_COUNTER_ID": "<value>",
"YANDEX_METRIKA_LOGS_DIR": "<value>"
}
}
}
}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 BoxLab-Ltd (GitHub)
| Server | Runs |
|---|---|
| Yandex Webmaster MCPQuery Yandex Webmaster indexing, queries, diagnostics and backlinks, and recrawl, via an AI agent. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| XploitScanSecurity scanner for AI-generated code. 30 free rules; all 214 with a paid-plan API key. | Local · stdio |
| 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 MetrikaMCP server for Yandex Metrika API - counters, goals, reports, segments, logs. | 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 |