Read-only MCP server for Yandex Metrika analytics. Query visits, sources, geography, devices and more in plain language — directly in Claude, Cursor, or any MCP client.
Score is being calculated.
List Yandex Metrika counters available to the token.
Returns each counter's id, name and site so you can pick a counter_id
for query. Read scope is enough.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| result | Yes |
Run a Reporting API query against a Metrika counter (aggregated stats).
Pass Metrika field names directly. Common ones:
Metrics (comma-separated): ym:s:visits, ym:s:users, ym:s:pageviews, ym:s:bounceRate, ym:s:avgVisitDurationSeconds, ym:s:newUsers
Dimensions (comma-separated, optional — groups the result): ym:s:date, ym:s:lastTrafficSource, ym:s:startURL, ym:s:deviceCategory, ym:s:regionCountry, ym:s:UTMSource
date1 / date2: YYYY-MM-DD or relative (today, yesterday, NdaysAgo). filters: Metrika filter expression, e.g. "ym:s:deviceCategory=='mobile'". sort: field to sort by; prefix with '-' for descending, e.g. "-ym:s:visits".
Returns the raw Reporting API response (query meta, totals and data rows).
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | ||
| date1 | No | 7daysAgo | |
| date2 | No | today | |
| limit | No | ||
| filters | No | ||
| metrics | Yes | ||
| counter_id | Yes | ||
| dimensions | No |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
list_countersquery
Add one secure layer between your agents and this server.