SkillFoxx

ya-metrics-mcp

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

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

Extended access

Why this level

  • Reads commercially sensitive traffic, conversion and sales data
  • The OAuth token grants access to every counter on the account within the metrika:read scope
All reasons and checks
Russian stack

mrkhachaturov/ya-metrics-mcpAuthor:mrkhachaturov

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/ya-metrics-mcp

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

Other ways to install

Access and checks

How we review

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

  • Reads commercially sensitive traffic, conversion and sales data
  • The OAuth token grants access to every counter on the account within the metrika:read scope

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

What it does

The server provides 31 tools across seven Yandex Metrika analytics areas. Account and counters: listing counters and goals, counter metadata. Traffic and sources: visits, a sources overview, search phrases, source types, search engine data, new users by source. Content analytics for Zen and Turbo publisher integration: sources, categories, authors, topics, articles. Demographics and devices: age, gender, device, browser and OS, page-depth. Geography: traffic by city and country. Performance and conversion: bounce rate and duration by entry page, goal conversion rates, SEO performance, conversion by source and landing page. Advanced and drill-down reports: e-commerce purchases, time series, Direct A/B experiment bounce rates, a browser report, hierarchical drill-down and segment comparison. Every tool is read-only and needs only the metrika:read scope, and many accept a limit parameter so large exports do not overflow the agent's context.

Who it is for. For marketers and analysts who want broad read-only Yandex Metrika analytics with zero risk of changing anything in the counter.

Good fit when

  • You want to compare traffic sources, devices or user segments over a period
  • You want goal and landing-page conversion without opening the Metrika interface
  • You have a Zen or Turbo integration and need content analytics on articles and authors

Not a fit when

  • You need to create or change goals, filters, segments or counters: the server only reads data
  • You do not have a Zen or Turbo integration: without it, the content-analytics tools return nothing

Example request

Compare mobile vs desktop users this month for counter 12345678

MCP

Transport
stdio
Authentication
API key

Environment variables

YANDEX_API_KEY required, secret
Yandex OAuth token with the metrika:read scope
YANDEX_TIMEOUT
Request timeout in seconds, defaults to 30
YANDEX_RETRIES
Number of retries on 5xx errors, defaults to 3

Limitations

It needs an OAuth token with only the metrika:read scope, but counter management is not available through the server at all. Content analytics only works with a Yandex Zen or Turbo integration on the counter, and the e-commerce report needs purchase tracking enabled. The package is distributed via uvx or run from source; the README does not mention a separate pip release.

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

FAQ

Can the server change anything in Metrika?

No, all 31 tools only read data; the metrika:read scope alone is enough, no write access is needed.

Why does content analytics return no data?

These tools require a Yandex Zen or Turbo integration on the counter; without it, article sources, categories and authors are unavailable.

Discussion

No questions or reviews yet.

All Yandex Metrica tools

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

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

README in short

The English README, with a Russian version as a separate file, describes the server as exposing 31 tools across seven analytics domains. It covers getting an OAuth token with only the metrika:read scope, and configuration for Claude Desktop and Cursor via uvx or running from source with uv run. Tools are grouped into tables: account and counters, traffic and sources, content analytics flagged as requiring a Zen or Turbo integration, demographics and devices, geography, performance and conversion, advanced and drill-down reports. It separately covers the limit parameter for controlling response size and an environment variable table for timeouts and retries.

README badge

Report a problem