SkillFoxx

Yandex Metrika MCP Server (Node.js)

A 25-tool read-only Yandex Metrika MCP server, a fork of an unmaintained project with fixes for broken report parameters

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

Extended access

Why this level

  • Reads traffic, conversion and sales data, including commercially sensitive statistics
All reasons and checks
Russian stack

ilyavorozhbit/yandex-metrika-mcpAuthor:IlyaVorozhbit

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

Install

Manual install

git clone https://github.com/IlyaVorozhbit/yandex-metrika-mcp.git
cd yandex-metrika-mcp
npm install
npm run build

Install and build from source, requires Node.js 18 or newer.

Access and checks

How we review

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

  • Reads traffic, conversion and sales data, including commercially sensitive statistics

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

What it does

The server provides 25 read-only tools for Yandex Metrika analytics: basic account info and visits, a traffic-source summary and types with search phrases, new-user acquisition effectiveness, content analytics by source, category, author, topic and article, demographics and devices, mobile versus desktop comparison, page depth, regional and organic-traffic geography, page and goal performance, organic search, e-commerce by category and region, a browser report, time-grouped data, and Direct A/B experiment bounce rates. The project is based on atomkraft/yandex-metrika-mcp, unmaintained since August 2025, and carries a bugfix series on top: several reports were sending invalid Reporting API attributes or silently ignoring their date-range parameters, which the author fixes and documents in the commit history.

Who it is for. For people who considered the original atomkraft/yandex-metrika-mcp and want the same set of reports, but with fixed dates and parameters.

Good fit when

  • You want a broad set of read-only Metrika reports with zero risk of accidental writes
  • You have run into a report ignoring the date range in the original atomkraft project
  • You need content analytics by article author and topic alongside regular traffic

Not a fit when

  • You need to create counters, goals, or upload offline data: the server is entirely read-only, with no write tools
  • You need active upstream support: the original project is unmaintained, and this fork is kept up by a single maintainer

Example request

Compare mobile and desktop traffic over the last month

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_API_KEY required, secret
Yandex OAuth token; the metrika:read scope alone is enough for reading

Limitations

There is no npm package; install is by cloning and building from source. It is maintained best-effort by one person, and issues and PRs go to this fork, not the original. The set of reports is fixed; adding a custom tool means editing the code.

How to disable. Remove the server from your MCP client config and revoke the OAuth token at oauth.yandex.ru.

FAQ

How does this differ from atomkraft/yandex-metrika-mcp?

It is a fork carrying a bugfix series: several reports sent invalid API attributes or ignored the date range, which the author fixes and maintains, while the original has been unmaintained since August 2025.

Are there any write tools?

No, all 25 tools only read analytics data; the metrika:read scope alone is enough.

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

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
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 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 Yandex Metrika MCP server with 31 tools for traffic, content, demographics, geography, conversions and e-commerce, metrika:read only

MCP serverExtended access2
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

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialAuthenticationRepository starsMain difference
Yandex Metrika MCP Server (Node.js) (this card)noAPI key1
MCP Yandex Metrica with counter managementnoAPI key1manage counters and goals
Yandex Metrika MCP Server (ymetrika-mcp)noAPI key0on FastMCP, with OpenTelemetry tracing
Yandex Metrika MCP with DuckDBnoAPI key0analyzes raw Metrika logs locally in DuckDB

README in short

The English README, with a Russian version as a separate file, honestly states its origin: a fork of atomkraft/yandex-metrika-mcp with a bugfix series for reports, maintained separately from upstream. It lists capabilities by analytics area, the Node.js 18+ requirement, build-from-source install steps, and detailed OAuth token instructions describing all five Metrika access scopes with a note that metrika:read alone is enough for reading. The full list of 25 tools is grouped by section: account, sources, content, behavior and demographics, geography, performance and conversion, e-commerce, browsers, advanced analytics. MIT license.

README badge

Report a problem