mcp-server-yandex-metrika

An MCP server, CLI and Pydantic models for the Yandex Metrika API: reports, counters, goals, filters, segments, logs and offline conversion uploads

  • 2 ★ on the repository
  • Last commit
MCP server

Broad access

Why this level

  • Can delete counters, goals, filters, segments and access grants
  • A token with metrika:write scope grants full control over the account's counters
  • Can upload offline conversions and expenses, affecting attribution data
All reasons and checks
Russian stack

dontsovcmc/mcp-server-yandex-metrika

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/mcp-server-yandex-metrika

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Can delete counters, goals, filters, segments and access grants
  • A token with metrika:write scope grants full control over the account's counters
  • Can upload offline conversions and expenses, affecting attribution data

This is third-party code. Review the repository files before installing.

What it does

The project ships an MCP server, a CLI utility and a library of typed Pydantic models on top of the Yandex Metrika API. Coverage is broad: tabular, time-series, drill-down and comparison reports from the Reporting API, full management of counters, goals, filters, segments, labels, operations and access grants with create, update and delete, account and delegate management, chart annotations, the Logs API for exporting visits and hits, and uploading offline conversions, calls, expenses and user parameters. Every MCP tool has a matching CLI command, and the package runs as an MCP server with no arguments or as a plain CLI with a command. Every request goes straight to the API from the local machine; the token is never sent anywhere but Yandex Metrika.

Who it is for. For analysts and marketers who need full control over Yandex Metrika, including creating goals and filters, not just reading reports.

Good fit when

  • You want to create or change a counter's goals, filters or segments right from a conversation with an agent
  • You need to export raw visit logs or upload offline conversions and calls
  • You want the same data both in a CLI for scripts and in MCP for an agent, without a second tool

Not a fit when

  • You want view-only access with zero risk of accidentally deleting a goal, filter or counter: delete tools are available here
  • You do not need this much breadth, just reports without managing goals and permissions: a narrower server would fit better

Example request

Create a Purchase goal of type url with a contain /thank-you condition for counter 12345678

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_METRIKA_TOKEN required, secret
Yandex Metrika OAuth token with metrika:read and metrika:write scopes
METRIKA_TIMEOUT
HTTP request timeout in seconds, defaults to 30
METRIKA_FILE_TIMEOUT
Log file download timeout in seconds, defaults to 60

Limitations

The repository metadata does not explicitly declare a license, though the README states MIT. It needs an OAuth token with metrika:read and metrika:write scopes. API limits: 30 requests per second per IP, 5,000 per day per user, 3 parallel requests, and a separate limit of 200 requests per 5 minutes for the main report endpoint; exceeding it returns HTTP 429.

How to disable. Remove the server with claude mcp remove yandex-metrika and revoke the OAuth token at oauth.yandex.com.

FAQ

Can the server be used without an MCP client?

Yes, the same package works as a plain CLI: with no arguments it starts the MCP server, and with a command like counters or stat-data it runs that request and prints JSON.

Are there typed models for custom scripts?

Yes, the package includes Pydantic models for every API object with extra=allow for forward compatibility, importable into your own Python programs.

Discussion

No questions or reviews yet.

MCP Yandex Metrica with counter management

@theyahia/yandex-metrika-mcp

Russian stack

Yandex Metrica MCP server with 15 tools: reports and traffic plus creating, editing, and deleting counters and goals

MCP serverBroad access1Repository stars
Editors’ pick

A Yandex Metrika MCP server generated from the API spec: 108 methods, 10 tools declared by default, transparent filters and response metadata

MCP serverExtended access2Repository stars

Yandex Metrica MCP

yandex-metrica-mcp

Russian stack

Read-only MCP server for Yandex Metrica: reports, period comparison, goals and raw log export with browser login

MCP serverExtended access15Repository stars

Yandex Metrika MCP

Yandex Metrika MCP Server

Russian stack

MCP server for Yandex Metrika reports: traffic, sources, search phrases, goals, geography, devices and content analytics

MCP serverExtended access24Repository stars
Russian stack

A minimalist Python MCP with 12 read-only tools using the correct OAuth header, paired with a skill that carries the period-comparison methodology

MCP serverExtended access4Repository stars

README in short

The Russian README describes three forms of one package: an MCP server, a CLI and a Pydantic model library on top of the Yandex Metrika API. It gives a detailed tool table by category: reports, counters, goals, filters, access, operations, segments, labels, accounts, annotations, access filters, Logs API, data import, each with a matching CLI name. It covers getting an OAuth token, installing via uvx and pip, connecting to Claude Code and Claude Desktop, a temporary --mcp-config connection, CLI command examples, using the Pydantic models in custom scripts, environment variables and API limits. MIT license.

README badge

Report a problem