SkillFoxx

Yandex Metrika MCP server, hardened read-only fork

yandex-metrika-mcp

A read-only MCP server for the Yandex Metrika Stat API, a fork of atomkraft with npx install and fixed report dates

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

Extended access

Why this level

  • Runs via npx from GitHub and reads Metrica reports with a metrika:read OAuth token
  • The code has no write operations
All reasons and checks
Russian stack

nikolaymokh-dev/yandex-metrika-mcpAuthor:nikolaymokh-dev

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

Install

Manual install

claude mcp add yandex-metrika --env YANDEX_API_KEY=ВАШ_ТОКЕН -- npx -y github:nikolaymokh-dev/yandex-metrika-mcp

Command from the README, installs and connects the server in one step.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Runs via npx from GitHub and reads Metrica reports with a metrika:read OAuth token
  • The code has no write operations

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

What it does

The server provides 26 tools over the Metrika Stat API: visits, traffic sources, content analytics, demographics, devices, geography, page depth, goal conversions, e-commerce and other reports. All tools only read data, there are no write operations in the project at all, so there is no flag to gate them. The project is forked from atomkraft/yandex-metrika-mcp and adds npx install straight from git, fixes date_from and date_to being ignored in get_visits, and returns errors as an MCP result with isError instead of plain text.

Who it is for. For analysts and marketers who want safe read-only access to a wide set of Metrika reports from an agent.

Good fit when

  • You need a wide set of ready Metrika reports: content analytics, devices, geography, e-commerce
  • It matters that the server cannot change anything in the account by design
  • You want a one-command install with claude mcp add and npx from github

Not a fit when

  • You need Logs API access or counter and goal management: not present here
  • You need Direct or Webmaster support in the same server

Example request

Compare mobile and desktop traffic for the week and show goal conversions

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_API_KEY required, secret
Yandex OAuth token with metrika:read scope

Limitations

The package is not published to the npm registry; install runs npx -y github:owner/repo straight from the repository. No access to the Logs API, import or management. An OAuth token with metrika:read scope is required.

How to disable. Remove the server with claude mcp remove yandex-metrika or delete it from .mcp.json.

FAQ

Can the server change anything in Metrika?

No, write operations are not implemented at all, only 26 reporting tools.

How does it differ from the original atomkraft project?

It adds npx install, fixes a bug where dates were ignored in get_visits, and changes error handling.

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
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 access4

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

A read-only MCP server for Yandex Metrika: reports with exact dates, time zone and sampling status, browser sign-in.

MCP serverExtended access130
Russian stack

A read-only Yandex Metrika MCP server with 31 tools for traffic, content, demographics, geography, conversions and e-commerce, metrika:read only

MCP serverExtended access2

README in short

The Russian README explains why the server is read-only by construction rather than by flag, how to get an OAuth token with metrika:read scope only, and gives three install paths: claude mcp add, a .mcp.json config, and building from source. Tools are grouped by topic: account, sources, content, audience, geography, behavior, search, e-commerce. English details live in README_en.md, and changes versus the original are listed in NOTICE.

README badge

Report a problem