Appmetrica MCP

What appmetrica-mcp MCP server does

The appmetrica-mcp MCP server exposes Yandex AppMetrica data and selected management operations as MCP tools. It can enumerate applications, retrieve application details, inspect client event names and configured conversions, and check whether the Logs API is available for the account.

Reporting tools cover aggregated metrics over a date range, time-series grouping by hour, day, week, or month, and dimension drilldowns. Reports accept options such as filters, sorting, segments, currency, accuracy, undefined-value handling, language, and pagination. A metric and dimension catalogue supports compact listing and filtered searches across the available definitions.

The server also includes tools for saved segments and funnels, ad-hoc funnel steps, funnel conversion results, dashboard presets, locally stored workspaces, and event instrumentation audits. The audit compares registered events with observed activity and can identify zero-volume or missing events for a selected period.

How it works

An MCP client starts the server, which calls AppMetrica APIs using a Yandex OAuth token. Read operations are available for account and application analytics. Write actions are protected by a setting that must be enabled explicitly; the README identifies push campaign creation and funnel or segment changes as write operations.

Local workspaces are represented as JSON data on the server’s filesystem. These differ from AppMetrica’s web workspaces. The web_* tools use an experimental logged-in Chrome session to inspect or modify AppMetrica workspaces, including their groups, headers, and widgets. This browser path is separate from the API-based reporting and management functions.

Setup and configuration

The appmetrica-mcp MCP server requires Node.js 22 or newer, an AppMetrica account with at least one application, and Yandex authorization. The recommended authentication command is npx appmetrica-mcp auth; it stores credentials locally for later server runs. An OAuth token can instead be supplied directly with APPMETRICA_OAUTH_TOKEN.

The standard installation pattern runs the package with npx -y appmetrica-mcp, including from Claude Code or Claude Desktop. APPMETRICA_ALLOW_WRITE=true enables supported write tools; its default is false. APPMETRICA_WORKSPACES_FILE changes the location of locally saved workspaces.

The experimental web tools additionally need Google Chrome or another configured Chromium-compatible browser and a one-time npx appmetrica-mcp login. Browser profile and executable settings can be controlled with APPMETRICA_BROWSER_PROFILE, APPMETRICA_BROWSER_PATH, and APPMETRICA_BROWSER_CHANNEL.

Tools and capabilities

Available capabilities include:

• Listing applications, events, conversions, segments, funnels, dashboard presets, workspaces, and report namespaces.
• Running reports, time series, drilldowns, saved or ad-hoc funnel reports, and metric catalogue searches.
• Checking Logs API status and auditing event instrumentation over a selected period.
• Reading and changing locally saved workspace definitions.
• Reading and editing AppMetrica web workspaces through the experimental browser session.

Limitations and notes

The server depends on AppMetrica account access and a valid Yandex OAuth authorization. Logs-related operations require the account’s Logs API availability. Browser workspace features are experimental and require a separate logged-in browser session. Write operations remain disabled unless explicitly enabled, so read-only behavior is the default.