Skip to content

Yandex Metrika MCP

by expremiental · remote · no sign-in to list tools · v0.1.0 · published by GitHub user expremiental

Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language.

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http yandex-metrika https://mcp.getaiaiai.ru/yandex-metrika

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 1Claude Code: ask
  • queryRun a Reporting API query against a Metrika counter (aggregated stats).No findings

    Why it is in this group

    • The name "query" says "query": a word for reading.
    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    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:<attribution>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).
Only reads 1Claude Code: allow
  • list_countersList Yandex Metrika counters available to the token.No findings

    Why it is in this group

    • The name "list_counters" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http yandex-metrika https://mcp.getaiaiai.ru/yandex-metrika

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__yandex-metrika__list_counters"
    ],
    "ask": [
      "mcp__yandex-metrika__query"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as yandex-metrika. Review it before you use it.