Yandex Metrica MCP vs Yandex Metrica
A side-by-side look at the Yandex Metrica MCP and Yandex Metrica MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Y
Yandex Metrica MCPMarketingYandex Metrica for AI agents: counters, goals, Reporting API and Logs API export over stdio.33EmergingAuth: not declaredVerdict: choose Yandex Metrica MCP for marketing work; choose Yandex Metrica for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
YChoose Yandex Metrica MCP when
- You need dedicated capabilities in the Marketing domain.
- You have the keys it needs:
YANDEX_METRICA_TOKEN.
Choose Yandex Metrica when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Y Yandex Metrica MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 33/100 · Emerging | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | YANDEX_METRICA_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Yandex Metrica MCP | View Yandex Metrica |
Tools & capabilities
Yandex Metrica MCP tools
No tool names declared yet. Check the project README from the listing page.
Yandex Metrica tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Yandex Metrica MCP
No confirmed install command for Yandex Metrica MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Yandex Metrica
{
"mcpServers": {
"yandex-metrica": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-metrica@latest"
]
}
}
}
Frequently asked questions
Yandex Metrica MCP is categorized under Marketing and uses an install path we have not confirmed yet. Yandex Metrica belongs to Marketing and uses a local stdio subprocess. Pick Yandex Metrica MCP for marketing work and Yandex Metrica for marketing.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Yandex Metrica MCP has no confirmed install command yet — follow its own setup instructions.
Yandex Metrica MCP has no declared pricing — check the project's own site. Yandex Metrica has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add yandex-metrica-mcp-2 and yandex-metrica as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Yandex Metrica MCP has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Yandex Metrica has 45/100 (Fair) with 2 views, 0 installs and 4 GitHub stars.