Yandex Metrica MCP vs Yandex Metrika MCP
A side-by-side look at the Yandex Metrica MCP and Yandex Metrika MCP 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 Metrika MCP 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 Metrika MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
YANDEX_METRIKA_TOKEN. - You want tools like
list_counters, get_counter, create_counter.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Y Yandex Metrica MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 33/100 · Emerging | 60/100 · Good |
| 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 | YANDEX_METRIKA_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 15 |
| Full listing | View Yandex Metrica MCP | View Yandex Metrika MCP |
Tools & capabilities
Yandex Metrica MCP tools
No tool names declared yet. Check the project README from the listing page.
Yandex Metrika MCP tools 15
list_countersList all Yandex.Metrica counters available to the authenticated user. Returns counter ID, name, site URL, and status. Supports search filtering.get_counterGet full details of a single Yandex.Metrica counter by ID, including configuration, code snippet status, and goals count.create_counterCreate a new Yandex.Metrica counter for a website. Returns the new counter ID and tracking code. You need to install the tracking code on the site afterwards.update_counterUpdate an existing Yandex.Metrica counter — change its name or site URL.delete_counterPermanently delete a Yandex.Metrica counter. This action is irreversible — all historical data for this counter will be lost.list_goalsList all goals configured for a Yandex.Metrica counter. Goals track conversions like page visits, button clicks, or multi-step funnels.create_goalCreate a new conversion goal for a counter. Supports types: 'url' (page visit), 'number' (page count threshold), 'step' (multi-step funnel), 'action' (JavaScript event).delete_goalDelete a conversion goal from a counter. Historical goal data in reports is preserved.export_logsExport raw visit or hit logs via the Logs API. Creates a log request and evaluates feasibility. Use source='visits' for session data, source='hits' for pageview data.get_reportFlexible Yandex.Metrica reporting endpoint. Query any combination of metrics (ym:s:visits, ym:s:pageviews, ym:s:bounceRate, ym:s:avgVisitDurationSeconds, ym:s:users, ym:s:newUsers, etc.) with dimensions (ym:s:trafficSource, ym:s:searchEngine, ym:s:country, ym:s:browser, ym:s:deviceCategory, ym:s:date, etc.) over a date range. Supports filters and sorting.get_report_comparisonCompare metrics between two date periods (A vs B). Useful for week-over-week, month-over-month, or campaign before/after analysis.get_report_drilldownDrill down into report data hierarchically. Start at top level, then pass parent_id to explore sub-dimensions (e.g., country -> city, traffic source -> campaign).- +3 more on 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 Metrika MCP
{
"mcpServers": {
"yandex-metrika-mcp-2": {
"command": "npx",
"args": [
"-y",
"@theyahia/yandex-metrika-mcp"
],
"env": {
"YANDEX_METRIKA_TOKEN": "YOUR_YANDEX_METRIKA_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Yandex Metrica MCP is categorized under Marketing and uses an install path we have not confirmed yet. Yandex Metrika MCP belongs to Marketing and uses a local stdio subprocess. Pick Yandex Metrica MCP for marketing work and Yandex Metrika MCP 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 Metrika MCP 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-metrika-mcp-2 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 Metrika MCP has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.