Appmetrica MCP vs Yandex Analytics
A side-by-side look at the Appmetrica MCP and Yandex Analytics 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 Analytics 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 Analytics 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 have the keys it needs:
YANDEX_MCP_DEFAULT_COUNTER, YANDEX_MCP_CLIENT_ID, YANDEX_MCP_KEYSTORE, YANDEX_MCP_SECRET_TOKEN, YANDEX_MCP_SECRET_METRIKA_TOKEN, YANDEX_MCP_DIRECT_SANDBOX, YANDEX_MCP_DIRECT_CLIENT_LOGIN, YANDEX_MCP_WORDSTAT_WAIT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Appmetrica MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 59/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | None listed | YANDEX_MCP_DEFAULT_COUNTERYANDEX_MCP_CLIENT_IDYANDEX_MCP_KEYSTOREYANDEX_MCP_SECRET_TOKENYANDEX_MCP_SECRET_METRIKA_TOKENYANDEX_MCP_DIRECT_SANDBOXYANDEX_MCP_DIRECT_CLIENT_LOGINYANDEX_MCP_WORDSTAT_WAIT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 4 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 45 | Not listed |
| Full listing | View Appmetrica MCP | View Yandex Analytics |
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 Analytics 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.
Appmetrica MCP
{
"mcpServers": {
"appmetrica-mcp": {
"command": "npx",
"args": [
"-y",
"appmetrica-mcp"
]
}
}
}
Yandex Analytics
{
"mcpServers": {
"yandex-analytics": {
"command": "uvx",
"args": [
"yandex-mcp"
],
"env": {
"YANDEX_MCP_DEFAULT_COUNTER": "YOUR_YANDEX_MCP_DEFAULT_COUNTER_HERE",
"YANDEX_MCP_CLIENT_ID": "YOUR_YANDEX_MCP_CLIENT_ID_HERE",
"YANDEX_MCP_KEYSTORE": "YOUR_YANDEX_MCP_KEYSTORE_HERE",
"YANDEX_MCP_SECRET_TOKEN": "YOUR_YANDEX_MCP_SECRET_TOKEN_HERE",
"YANDEX_MCP_SECRET_METRIKA_TOKEN": "YOUR_YANDEX_MCP_SECRET_METRIKA_TOKEN_HERE",
"YANDEX_MCP_DIRECT_SANDBOX": "YOUR_YANDEX_MCP_DIRECT_SANDBOX_HERE",
"YANDEX_MCP_DIRECT_CLIENT_LOGIN": "YOUR_YANDEX_MCP_DIRECT_CLIENT_LOGIN_HERE",
"YANDEX_MCP_WORDSTAT_WAIT": "YOUR_YANDEX_MCP_WORDSTAT_WAIT_HERE"
}
}
}
}
Frequently asked questions
Appmetrica MCP is categorized under Marketing and uses a local stdio subprocess. Yandex Analytics belongs to Marketing and uses a local stdio subprocess. Pick Appmetrica MCP for marketing work and Yandex Analytics 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 Analytics is listed as free. Auth: oauth 2.0. 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-analytics 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 Analytics has 41/100 (Fair) with 3 views, 0 installs and 4 GitHub stars.