Appmetrica MCP vs Yandex Metrika MCP
A side-by-side look at the Appmetrica 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.
A
Appmetrica MCPMarketing · Local subprocess (stdio)AppMetrica (Yandex) analytics: reports, funnels, segments, dashboards, logs export, push59GoodAuth: oauth 2.0Verdict: choose Appmetrica MCP for marketing work as a local process; 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?
AChoose Appmetrica MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
list_applications, get_application, list_events.
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 | A Appmetrica MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 59/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | YANDEX_METRIKA_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 45 | 15 |
| Full listing | View Appmetrica MCP | View Yandex Metrika MCP |
Tools & capabilities
Appmetrica MCP tools 45
list_applicationsList all AppMetrica applications in your accountget_applicationGet details for a specific application by IDlist_eventsList client event names of an application (use them as funnel steps)list_conversionsList configured conversions (attributed events)get_logs_api_statusCheck whether the Logs API is enabled for the accountget_reportAggregated metrics for a date range, with `filters`, `sort`, `segment_id`, `currency`, `accuracy`, `include_undefined`, `lang`, `offsetget_report_bytimeThe same as a time series (`group`: day / week / month / hour / all). One namespace prefix per callget_drilldownDrill down into a dimension value for detailed breakdownlist_metricsMetric/dimension catalogue (197 metrics, 188 dimensions): compact overview, or `search` / `namespace` / `kind` / `limit` for entriesaudit_eventsEvent instrumentation audit for a period: registered vs active vs zero-volume events, optional `expected_events`, plain-language findings (read-only)list_segmentsList saved segments (id, name, expression)get_segmentGet one segment with all fields- +33 more on 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.
Appmetrica MCP
{
"mcpServers": {
"appmetrica-mcp": {
"command": "npx",
"args": [
"-y",
"appmetrica-mcp"
]
}
}
}
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
Appmetrica MCP is categorized under Marketing and uses a local stdio subprocess. Yandex Metrika MCP belongs to Marketing and uses a local stdio subprocess. Pick Appmetrica 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.
Appmetrica MCP has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 appmetrica-mcp and yandex-metrika-mcp-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Appmetrica MCP has a quality signal of 59/100 (Good) with 1 views, 0 installs and 3 GitHub stars. Yandex Metrika MCP has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.