Appmetrica-mcp Server

AppMetrica (Yandex) analytics: reports, funnels, segments, dashboards, logs export, push

Local serverstdio

What is the Appmetrica-mcp Server?

Appmetrica-mcp is an MCP integration. AppMetrica (Yandex) analytics: reports, funnels, segments, dashboards, logs export, push.

Packages and local setup

The published npm package is appmetrica-mcp, version 0.3.1. Its declared MCP transport is stdio.

The package declares APPMETRICA_OAUTH_TOKEN: Yandex OAuth token with AppMetrica scope; optional when npx appmetrica-mcp auth saved credentials; APPMETRICA_ALLOW_WRITE: Set to "true" to enable write tools (funnels, segments, push campaigns, web workspaces); APPMETRICA_WORKSPACES_FILE: Path of the local JSON file with saved dashboard widget sets (default ~/.config/appmetrica-mcp/workspaces.json); APPMETRICA_BROWSER_PROFILE: Chrome profile directory for the experimental web session (default ~/.config/appmetrica-mcp/chrome-profile); APPMETRICA_BROWSER_PATH: Path to a Chrome/Chromium executable for the experimental web session (default: system Google Chrome); APPMETRICA_BROWSER_CHANNEL: Playwright browser channel for the experimental web session (chrome | chromium | msedge; default chrome); APPMETRICA_BROWSER_IDLE_MS: Idle time after which the headless web session closes Chrome and frees the profile (default 120000); APPMETRICA_OAUTH_CLIENT_ID: Your own Yandex OAuth app ClientID for appmetrica-mcp auth (default: bundled public app); APPMETRICA_CREDENTIALS_FILE: Where appmetrica-mcp auth stores the token (default ~/.config/appmetrica-mcp/credentials.json).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.3.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
APPMETRICA_OAUTH_TOKENYandex OAuth token with AppMetrica scope; optional when npx appmetrica-mcp auth saved credentialsOptional
APPMETRICA_ALLOW_WRITESet to "true" to enable write tools (funnels, segments, push campaigns, web workspaces)Optional
APPMETRICA_WORKSPACES_FILEPath of the local JSON file with saved dashboard widget sets (default ~/.config/appmetrica-mcp/workspaces.json)Optional
APPMETRICA_BROWSER_PROFILEChrome profile directory for the experimental web session (default ~/.config/appmetrica-mcp/chrome-profile)Optional
APPMETRICA_BROWSER_PATHPath to a Chrome/Chromium executable for the experimental web session (default: system Google Chrome)Optional
APPMETRICA_BROWSER_CHANNELPlaywright browser channel for the experimental web session (chrome | chromium | msedge; default chrome)Optional
APPMETRICA_BROWSER_IDLE_MSIdle time after which the headless web session closes Chrome and frees the profile (default 120000)Optional
APPMETRICA_OAUTH_CLIENT_IDYour own Yandex OAuth app ClientID for appmetrica-mcp auth (default: bundled public app)Optional
APPMETRICA_CREDENTIALS_FILEWhere appmetrica-mcp auth stores the token (default ~/.config/appmetrica-mcp/credentials.json)Optional