MCP Yandex Metrica with counter management
@theyahia/yandex-metrika-mcp
Yandex Metrica MCP server with 15 tools: reports and traffic plus creating, editing, and deleting counters and goals
- 1 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Can irreversibly delete a Yandex Metrica counter
- Can create and delete goals, affecting conversion data
- No separation of read-only and write modes at the server configuration level
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/theyahia-yandex-metrika-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can irreversibly delete a Yandex Metrica counter
- Can create and delete goals, affecting conversion data
- No separation of read-only and write modes at the server configuration level
This is third-party code. Review the repository files before installing.
What it does
The server provides 15 tools across four Yandex Metrica API areas. Counter management: list, details by ID, create new counter, rename or change site URL, and irreversible deletion. Goal management: list, create with types url, number, step, action, and delete. Logs: export raw visit and hit data via Logs API. Reports: flexible reports with any metrics, dimensions, filters, sorting, comparison of two periods, and hierarchical drill-down. Convenient wrappers: traffic summary, source breakdown by channels, and top pages by views. The server can run locally via stdio using npx or as an HTTP server for remote and multi-client scenarios with /mcp endpoint and /health health check. Includes ready smithery.yaml and analytics-report skill for Claude Code.
Who it is for. For marketers and agencies who need to read Metrica reports and create counters and goals directly from agent dialogs.
Good fit when
- Need to quickly create a new counter or goal for a new project
- Need a flexible report with custom metrics and period comparison
- Need a remote HTTP mode for multiple clients instead of local stdio
Not a fit when
- Require strictly read-only access without risk of accidentally deleting counters or goals: delete_counter is irreversible and available without extra confirmation
- Plan to issue a token with read-only rights only: the server uses a common OAuth Bearer token without read/write scope separation in configuration
Example request
Compare traffic from last week with the previous week for counter 12345678MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
YANDEX_METRIKA_TOKENrequired, secret- Yandex OAuth 2.0 Bearer token
Limitations
Counter deletion is irreversible, as noted in the README. Requires a Yandex OAuth Bearer token; the README shows how to get a token with read-only statistics access, though the server also provides write tools, so a token with broader permissions is needed for writing, obtained separately. There is no separation of read-only and write tools at the server configuration level.
How to disable. Remove the server with the command claude mcp remove yandex-metrika and revoke the OAuth token at oauth.yandex.ru.
FAQ
Can counter deletion be undone?
No, the README clearly states that delete_counter removes the counter irreversibly.
Can the server run as a remote HTTP endpoint?
Yes, the --http and --port flags start the server as a streamable HTTP service with /mcp endpoint and /health health check for multiple clients.
Discussion
No questions or reviews yet.
Related
All Yandex Metrica toolsYandex Metrica MCP: reports and goals in Claude, Cursor and Codex
mcp-yandex-metrica
A Metrica MCP server run with npx and Yandex OAuth sign-in inside the chat: counters, goals, visit and conversion reports, read-only by default
A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata
An MCP server, CLI and Pydantic models for the Yandex Metrika API: reports, counters, goals, filters, segments, logs and offline conversion uploads
Yandex Metrica MCP
yandex-metrica-mcp
Read-only MCP server for Yandex Metrica: reports, period comparison, goals and raw log export with browser login
Yandex Metrika MCP
Yandex Metrika MCP Server
MCP server for Yandex Metrika reports: traffic, sources, search phrases, goals, geography, devices and content analytics
Read-only Yandex Metrika MCP server
yandex-metrika-mcp
A minimalist Python MCP with 12 read-only tools using the correct OAuth header, paired with a skill that carries the period-comparison methodology
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| MCP Yandex Metrica with counter management (this card) | no | API key | 1 | |
| Yandex Metrika MCP Server (Node.js) | no | API key | 1 | fixed report bugs |
| Yandex Metrika MCP Server (ymetrika-mcp) | no | API key | 0 | on FastMCP, with OpenTelemetry tracing |
| Yandex Metrika MCP with DuckDB | no | API key | 0 | analyzes raw Metrika logs locally in DuckDB |
README in short
The README in English describes the server as part of the Russian API MCP series by theYahia. It includes instructions for obtaining an OAuth token with read-only statistics access, installation for Claude Desktop and Claude Code via npx, running in streamable HTTP mode for remote scenarios, and via Smithery. The table of 15 tools is divided into counter management, goals, logs, reports, and convenient wrappers for traffic, sources, and top pages. Demo prompts and development commands are provided. Licensed under MIT.