Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@yandex-metrika-mcp show me the traffic report for the last 7 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for Yandex Metrika Reports API (/stat/v1/*) and Management API (/management/v1/*).
Exposes 68 tools: 6 report tools and 62 management tools (counters, goals, filters, grants, segments, labels, and more).
Node.js 20+
OAuth token with metrika:read (reports) and/or metrika:write (create/update/delete)
Related MCP server: Yandex Direct MCP
Create a Yandex OAuth app — choose For API access or debugging.
Add permissions metrika:read (reports) and metrika:write (management changes).
Copy the app Client ID.
Open in browser:
https://oauth.yandex.ru/authorize?response_type=token&client_id=<CLIENT_ID>Copy the token from the redirect URL (access_token=...).
See Yandex Metrika authorization docs.
Add to .cursor/mcp.json or Cursor MCP settings:
From GitHub (builds dist via prepare on install):
{
"mcpServers": {
"yandex-metrika": {
"command": "npx",
"args": ["-y", "github:Rezlazy/yandex-metrika-mcp"],
"env": {
"METRIKA_TOKEN": "<your-oauth-token>"
}
}
}
}The default branch includes prepare. Pin a release with github:Rezlazy/yandex-metrika-mcp#v0.2.2 (v0.2.0 does not build from git).
For local development (.cursor/mcp.json in this repo):
{
"mcpServers": {
"yandex-metrika": {
"type": "stdio",
"command": "node",
"args": ["${workspaceFolder}/dist/index.js"],
"envFile": "${workspaceFolder}/.env"
}
}
}Create .env in the project root:
METRIKA_TOKEN=your_oauth_tokenVariable | Required | Description |
| yes | OAuth token ( |
| no | API base URL (default: |
*.code-workspace)If you open mcp.code-workspace (several folders in one window), Cursor may not show project MCP servers from .cursor/mcp.json in Settings → MCP. This is a known Cursor limitation.
Workarounds:
Open this repo directly: File → Open Folder → yandex-metrika-mcp (not the .code-workspace file).
Or add to global config ~/.cursor/mcp.json (works in multi-root):
"yandex-metrika": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/yandex-metrika-mcp/dist/index.js"],
"envFile": "/absolute/path/to/yandex-metrika-mcp/.env"
}After config changes: Refresh MCP in settings or restart Cursor. Check logs: Output panel → MCP Logs.
stat_*) — 6 toolsTool | Description |
| Table report |
| Time series (charts, trends) |
| Tree / drill-down report |
| Compare two segments (A vs B) |
| Segment comparison with drill-down |
| Pivot table |
mgmt_*) — 62 toolsCovers Management API: counters, goals, filters, operations, grants, access filters, segments, chart annotations, labels, accounts, delegates, clients, cloud exports.
Common management tools:
Tool | Description |
| List available counters |
| Get counter details |
| Create counter |
| List counter goals |
| Create goal |
| List access grants |
| List saved segments |
For POST/PUT methods pass JSON in the body parameter (see API formats). Example for creating a counter:
{
"body": {
"counter": {
"name": "My site",
"site": "example.com"
}
}
}ids — counter ID(s), comma-separated
metrics — e.g. ym:s:visits, ym:s:users, ym:s:pageviews
dimensions — e.g. ym:s:trafficSource, ym:s:operatingSystem
date1 / date2 — period (7daysAgo, today, or YYYY-MM-DD)
filters — segmentation expression
preset — report preset
format — json (default) or csv
Full list of metrics and dimensions: attrandmetr.
Tool: stat_data
{
"ids": "44147844",
"metrics": "ym:s:visits,ym:s:users",
"dimensions": "ym:s:trafficSource",
"date1": "30daysAgo",
"date2": "today",
"sort": "-ym:s:visits",
"limit": "10"
}Tool: stat_bytime
{
"ids": "44147844",
"metrics": "ym:s:visits",
"date1": "30daysAgo",
"date2": "today",
"group": "day"
}npm install
npm run typecheck
npm test
npm run buildSee CHANGELOG.md.
MIT
https://yandex.ru/dev/metrika/ru/management/ Create access filter. Body: {"access_filter": {...}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete access filter
Inputs: counterId (required), accessFilterId (required), pretty, delete_grants.
https://yandex.ru/dev/metrika/ru/management/ Get access filter by ID
Inputs: counterId (required), accessFilterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List access filters for counter
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Update access filter. Body: {"access_filter": {...}}
Inputs: body (required), counterId (required), accessFilterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete linked account
Inputs: user_login (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List linked Yandex accounts
Inputs: pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ Update accounts list. Body: {"accounts": [{"user_login": "..."}]}
Inputs: body (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create chart annotation. Body: {"chart_annotation": {...}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete chart annotation
Inputs: id (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Get chart annotation by ID
Inputs: id (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List chart annotations
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Update chart annotation. Body: {"chart_annotation": {...}}
Inputs: id (required), body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List available Direct clients
Inputs: pretty, counters.
https://yandex.ru/dev/metrika/ru/management/ Disable cloud export on counter
Inputs: ceId (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List Yandex Cloud export objects for counter
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create counter. Body: {"counter": {"site": "example.com", "name": "..."}}
Inputs: body (required), ytm, field, pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete counter
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Get counter by ID
Inputs: counterId (required), field, pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ Attach counter to label
Inputs: labelId (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Detach counter from label
Inputs: labelId (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List available counters
Inputs: sort, type, field, offset, +11 more.
https://yandex.ru/dev/metrika/ru/management/ Restore deleted counter
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Update counter. Body: {"counter": {...}}
Inputs: body (required), counterId (required), field, pretty.
https://yandex.ru/dev/metrika/ru/management/ Add delegate. Body: {"delegate": {"user_login": "..."}}
Inputs: body (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Remove delegate
Inputs: user_login (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List delegates
Inputs: pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ Create filter. Body: {"filter": {...}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete filter
Inputs: filterId (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Get filter by ID
Inputs: filterId (required), counterId (required), pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ List counter filters
Inputs: counterId (required), pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ Update filter. Body: {"filter": {...}}
Inputs: body (required), filterId (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create goal. Body: {"goal": {...}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete goal
Inputs: goalId (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Get goal by ID
Inputs: goalId (required), counterId (required), pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ List counter goals
Inputs: counterId (required), pretty, callback, useDeleted.
https://yandex.ru/dev/metrika/ru/management/ Update goal. Body: {"goal": {...}}
Inputs: body (required), goalId (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create grant. Body: {"grant": {"user_login": "...", "perm": "view"}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete grant
Inputs: counterId (required), pretty, user_uid, user_login.
https://yandex.ru/dev/metrika/ru/management/ Get grant for user
Inputs: counterId (required), user_login (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List counter access grants
Inputs: counterId (required), pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ Update grant. Body: {"grant": {...}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create label. Body: {"label": {"name": "..."}}
Inputs: body (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete label
Inputs: labelId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Get label by ID
Inputs: labelId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List user labels
Inputs: pretty.
https://yandex.ru/dev/metrika/ru/management/ Update label. Body: {"label": {"name": "..."}}
Inputs: body (required), labelId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List messengers for messenger goal type
Inputs: pretty.
https://yandex.ru/dev/metrika/ru/management/ Get current user grant for counter
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create operation. Body: {"operation": {...}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete operation
Inputs: counterId (required), operationId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Get operation by ID
Inputs: counterId (required), operationId (required), pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ List counter operations
Inputs: counterId (required), pretty, callback.
https://yandex.ru/dev/metrika/ru/management/ Update operation. Body: {"operation": {...}}
Inputs: body (required), counterId (required), operationId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create public grant (no body)
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete public grant
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Create segment. Body: {"segment": {...}}
Inputs: body (required), counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Delete segment
Inputs: counterId (required), segmentId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Get segment by ID
Inputs: counterId (required), segmentId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List counter segments
Inputs: counterId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ Update segment. Body: {"segment": {...}}
Inputs: body (required), counterId (required), segmentId (required), pretty.
https://yandex.ru/dev/metrika/ru/management/ List social networks for social goal type
Inputs: pretty.
Yandex Metrika Reports API. Docs: https://yandex.ru/dev/metrika/ru/stat/ Time series report — GET /stat/v1/data/bytime. Use for charts and trends.
Inputs: ids (required), metrics (required), lang, sort, +16 more.
Yandex Metrika Reports API. Docs: https://yandex.ru/dev/metrika/ru/stat/ Segment comparison table — GET /stat/v1/data/comparison. Compare segments A and B with separate date ranges and filters.
Inputs: ids (required), metrics (required), lang, sort, +19 more.
Yandex Metrika Reports API. Docs: https://yandex.ru/dev/metrika/ru/stat/ Segment comparison drill-down — GET /stat/v1/data/comparison/drilldown. Tree report comparing segments A and B.
Inputs: ids (required), metrics (required), lang, sort, +21 more.
Yandex Metrika Reports API. Docs: https://yandex.ru/dev/metrika/ru/stat/ Table report — GET /stat/v1/data. Returns rows with dimensions and metrics.
Inputs: ids (required), metrics (required), lang, sort, +13 more.
Yandex Metrika Reports API. Docs: https://yandex.ru/dev/metrika/ru/stat/ Drill-down tree report — GET /stat/v1/data/drilldown. One tree level per request; use parent_id for nested levels.
Inputs: ids (required), metrics (required), lang, sort, +15 more.
Yandex Metrika Reports API. Docs: https://yandex.ru/dev/metrika/ru/stat/ Pivot table — GET /stat/v1/data/pivot. Rows by dimensions, columns by pivot_dimensions.
Inputs: ids (required), metrics (required), lang, sort, +16 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 68 tools
The tools are mostly distinguishable by resource/action naming (counters, goals, filters, segments, etc.), and the stat_* report variants target distinct report types. However, with 68 tools, an agent may hesitate between similar pairs such as stat_data vs stat_bytime or filter vs access_filter, so it is not a perfect 5.
The mgmt_<resource>_<action> pattern is used consistently across the management tools, and stat_* prefixes all report endpoints. Minor deviations like mgmt_counter_undelete, mgmt_cloud_export_remove, mgmt_accounts_update, and stat_data (noun-only) keep it from being fully uniform.
68 tools is far beyond the recommended 3-15 range and will make tool selection difficult for an agent, even though the underlying Yandex Metrika API is broad. This is too many for a coherent MCP surface.
The set covers the six main report variants and provides full CRUD-style coverage for most management resources, including counters, goals, filters, operations, grants, segments, and annotations. Minor gaps exist (e.g., no create/update for public grants or cloud exports, and no Logs API tools), but the main workflows are supported.
Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language.
Analyze Yandex Metrica traffic and conversions in ChatGPT with read-only access.
Read and manage OnyxMetric web analytics: traffic, errors, funnels, goals, sites and segments.
MCP servers for Yandex APIs: Wordstat, Search, Webmaster, Metrika, Direct. Open source, by Seyka AI.