SkillFoxx

Yandex Metrika MCP: 68 Reports and Management API tools

@rezlazy/yandex-metrika-mcp

An MCP server with 68 Metrika tools: 6 reporting and 62 management tools for counters, goals, filters, access and segments

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • 62 management tools create, edit and delete counters, goals, filters and access grants
  • A token with metrika:write can change settings on live counters
All reasons and checks
Russian stack

rezlazy/yandex-metrika-mcpAuthor:Rezlazy

A similar tool with a larger community: Yandex Metrika MCP, 24 ★ on the repository

Install

Manual install

{
  "mcpServers": {
    "yandex-metrika": {
      "command": "npx",
      "args": ["-y", "github:Rezlazy/yandex-metrika-mcp#v0.2.2"],
      "env": {
        "METRIKA_TOKEN": "<your-oauth-token>"
      }
    }
  }
}

For .cursor/mcp.json or Cursor MCP settings; the tag pins a working release.

Access and checks

How we review

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

  • 62 management tools create, edit and delete counters, goals, filters and access grants
  • A token with metrika:write can change settings on live counters

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

What it does

The server wraps the Yandex Metrika Reports API and Management API. Six reporting tools cover a table report, time series, drilldown, segment comparison, comparison with drilldown, and a pivot table. 62 management tools work with the Management API: listing and creating counters, goals, filters, operations, access grants, segments, chart annotations, labels, accounts, trusted delegates, clients and cloud exports. POST and PUT requests pass JSON directly in the body parameter following the Management API format. Installs as a GitHub package via npx or locally from source.

Who it is for. For agencies and analysts who need to manage many Metrika counters and their settings, not just read reports.

Good fit when

  • You need to bulk-create or configure goals and segments across several counters
  • You need to manage counter access and trusted delegates through an agent
  • You want both reporting and admin actions in one server instead of two separate tools

Not a fit when

  • You only need read-only reports: 62 management tools create risk of accidental setting changes
  • You work in a multi-root Cursor workspace: a known limitation prevents picking up the project .cursor/mcp.json

Example request

Create a new goal for visiting the checkout page in counter 44147844 and show the top 10 traffic sources by visits over 30 days

MCP

Transport
stdio
Authentication
OAuth

Environment variables

METRIKA_TOKEN required, secret
OAuth token with metrika:read and optionally metrika:write scope
METRIKA_API_URL
API base URL, defaults to api-metrika.yandex.net

Limitations

Requires an OAuth token with metrika:read and, for management operations, metrika:write scope. In multi-root Cursor workspaces the project .cursor/mcp.json may not be picked up; the README documents workarounds via opening the folder directly or a global config. Version v0.2.0 does not build from git, so a newer tag must be pinned.

How to disable. Remove the yandex-metrika block from .cursor/mcp.json or another MCP client config.

FAQ

Why doesn't Cursor see the server from the project config?

A known Cursor limitation with multi-root workspaces: open the repo as its own folder, or add the server to the global ~/.cursor/mcp.json.

How do I pass data to create a counter or goal?

Pass JSON in the body parameter of the management tool, in the format the Metrika Management API expects.

How is the 68-tool Yandex Metrika MCP different from other Metrika servers?

The server wraps the Metrika Reports API and Management API. Six report tools cover a table report, time series, drilldown, segment comparison and a pivot table, and 62 management tools work with counters, goals, filters, access and segments.

How do I pass data to create a counter or goal and why does Cursor not see the server?

Counter and goal parameters are passed in tool arguments, formats are in the README. If Cursor does not see the server from a project config, check the .cursor/mcp.json file and restart the editor. It works in Cursor. Risk is high because the server changes counter settings.

Discussion

No questions or reviews yet.

All Yandex Metrica tools

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 access1
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 access2

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 access24
Russian stack

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

MCP serverBroad access2

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 access15

README in short

The README covers requirements and getting an OAuth token, a Cursor config via npx with a pinned release, a section on the multi-root workspace limitation, tables of reporting and commonly used management tools, report parameter descriptions with visits-by-source and daily-trend examples, and development commands.

README badge

Report a problem