Yandex Metrika MCP: a compact reporting server
yandex-metrika-mcp-server
A small MCP server for the Yandex Metrika Reports API on the official SDK, with no extra tools or settings
Low risk
We rate an entry low when it mostly gives the agent instructions and reference material.
Why this level
- Based on the code it only calls Reports API reporting methods; no write calls are visible
Install
Manual install
git clone https://github.com/clientssukach-lang/yandex-metrika-mcp-server.git
cd yandex-metrika-mcp-server
npm installInstalls dependencies; the repository has no README.
This is third-party code. Review the repository files before installing.
What it does
The server is built on the official MCP SDK, Express and Zod, and calls the Yandex Metrika Reports API with an OAuth token. All the code fits into one server.js file, compiled from TypeScript sources, and it supports both stdio and Streamable HTTP transport. Clear error hints are built into the code: on a 400 it suggests checking metric and dimension names and the date format, and on a 401 it suggests reissuing the token, which noticeably simplifies debugging compared to raw API errors.
Who it is for. For developers who want a minimal Metrika reporting server without extensive docs or extra configuration.
Good fit when
- You want a small, easy-to-read Metrika reporting server in a single file
- Working only with the Reports API, without managing counters and goals, is enough
- You want clear hints about auth and request format errors right in the response
Not a fit when
- You need to manage counters, goals or segments: the server only offers reports
- You need thorough documentation: there is no README, so you need to read the code
Example request
Show visits and pageviews for counter 44147844 over the last 30 daysLimitations
The repository has no README: variable purposes and call formats are visible only from server.js and package.json. Works only with the Reports API; the Management API is not available. Requires a Metrika OAuth token.
How to disable. Remove the yandex-metrika-mcp-server block from your MCP client config.
MCP
- Transport
- stdio, http
- Authentication
- OAuth
| Environment variables | |
|---|---|
| METRIKA_OAUTH_TOKEN required, secret | Yandex Metrika OAuth token |
| METRIKA_API_BASE_URL | API base URL, defaults to api-metrika.yandex.net |
Security check
- Based on the code it only calls Reports API reporting methods; no write calls are visible
README in short
There is no README. package.json shows the name yandex-metrika-mcp-server, the modelcontextprotocol/sdk, express and zod dependencies, and the node server.js run command. The server.js code shows calls to api-metrika.yandex.net using the METRIKA_OAUTH_TOKEN token, with 400, 401 and 403 errors handled with clear hints.
FAQ
Why is there no README?
The repository has no README; the server's purpose and variables are clear from package.json and the server.js code.
Can counters be managed through this server?
No, based on the code it only calls the Metrika Reports API; the Management API is not implemented.
Related
Official DataLens (Yandex) skills for Claude Code, Codex and OpenCode: SDK, HTML reports and RLS resolution
A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata
An open MCP server and agent skill set for SEO: keyword research, competitors, backlinks and site audits powered by DataForSEO
A Claude Code plugin for SEO audits: technical SEO, E-E-A-T, schema, local and AI search via parallel subagents