Appmetrica MCP server

AppMetrica MCP — Yandex App Metrica MCP server for Claude and AI agents

MCP server for AppMetrica — Yandex's mobile analytics platform. Gives Claude direct access to your app's analytics: reports, funnels, dashboards, raw event logs, crash data, and push notification campaigns — and can create funnels and segments in AppMetrica itself.

Update 0.3.0 (October 2026). The server now builds analytics in AppMetrica, not only reads it: saved funnels and segments through the Management API, and real workspaces/dashboards through an experimental logged-in Chrome session (web tools, one-time npx appmetrica-mcp login). Also new: time series (getreportbytime), a docs-derived catalogue of 197 metrics, all 13 Logs API tables, auditevents and the analytics_setup workflow prompt. Full list in CHANGELOG.md.

Why

AppMetrica keeps mobile product analytics (users, sessions, events, funnels, retention, revenue, crashes) behind a web UI and several HTTP APIs. This MCP server puts all of it behind one set of tools, so an AI agent such as Claude can answer and act on questions like:

• "How did DAU, new users and crash-free sessions change this week?"
• "Build a funnel from first launch to purchase and save it in AppMetrica."
• "Which events does the app send, which ones are dead, and what is missing for a registration funnel?"
• "Create a workspace with audience, revenue and funnel widgets for the marketing team."
• "Export raw purchase events for September and compare countries."

It works with Claude Code, Claude Desktop and any other MCP client, and is listed in the official MCP Registry as io.github.pavellunev/appmetrica-mcp.

Features

• Reporting API — aggregated metrics (users, sessions, revenue, crashes, events, ...) with dimension breakdowns, time series (bytime), filters, sorting and sampling control
• Funnels — step-by-step funnel reports for saved web-UI funnels or ad-hoc steps, with absolute/relative conversion; create, update and delete saved funnels
• Dashboards & Workspaces — preset or custom widget sets computed from the Reporting API; named widget sets saved locally as workspaces
• Web session (experimental) — create and manage real AppMetrica workspaces (dashboards) and widgets through a logged-in headless Chrome session (web_* tools; the public API cannot do this)
• Segments — list saved segments and apply them to any report via segment_id; create, update and delete segments
• Event audit — audit_events compares registered events with real volumes and reports instrumentation gaps
• Workflow prompt — analytics_setup walks an agent through analysing an app, building funnels/segments/dashboards and listing instrumentation gaps
• Logs API — raw exports for all 13 tables (events, crashes, errors, installations, sessions, deeplinks, postbacks, clicks, push tokens, profiles, revenue, e-commerce, ad revenue)
• Management API — applications, event names, conversions, Logs API status
• Push API — view campaigns and statistics; create campaigns when write mode is enabled
• Safe by default — write operations (push campaigns, funnels, segments) are disabled unless you explicitly opt in

Requirements

• Node.js 22+
• An AppMetrica account with at least one application
• A Yandex OAuth token (see below)
• Optional, only for the experimental web_* tools: Google Chrome and a one-time npx appmetrica-mcp login (see Web session)

Getting an OAuth Token

Option A — one command (recommended)

npx appmetrica-mcp auth

Shortened. The full README is on GitHub.