SkillFoxx

Yandex Metrica MCP: reports and goals in Claude, Cursor and Codex

mcp-yandex-metrica

A Metrica MCP server run with npx and Yandex OAuth sign-in inside the chat: counters, goals, visit and conversion reports, read-only by default

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

Extended access

Why this level

  • The generic request with confirmWrite=true can change and delete Metrica objects
  • By default the server sends anonymous usage telemetry to an external address
All reasons and checks
Russian stack

askads/mcp-yandex-metricaAuthor:Ask Ads

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/mcp-yandex-metrica

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.

  • The generic request with confirmWrite=true can change and delete Metrica objects
  • By default the server sends anonymous usage telemetry to an external address

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

What it does

The Node.js 20 server gives an agent eight tools: counter list, goal list, a `get_statistics` report, connecting and disconnecting access and a generic request to the Metrica API. Reports show visits, users, pageviews, bounces, visit duration, sources, devices and goal completions for a period, with totals and a sampling flag. Sign-in happens in chat: the server hands out a Yandex OAuth link, you send back a one-time code valid for 10 minutes, and it is exchanged for a token with PKCE. The token is stored in ~/.config/mcp-yandex-metrica/credentials.json with owner-only rights.

Who it is for. Site owners, marketers and SEO specialists who watch Yandex Metrica traffic and want to ask about it in a chat with an agent.

Good fit when

  • You want traffic sources and goal conversion for a month without opening the Metrica interface
  • An agent should find the right goal and build a report on it
  • The server is connected in CI or a non-standard environment through a token in an environment variable
  • You want access to several counters with a default one

Not a fit when

  • You need writing to Metrica: dedicated tools only read, and writing goes only through the generic request with confirmation
  • Anonymous telemetry is not acceptable: by default the server sends depersonalised usage events
  • You need Yandex Direct or Webmaster data: the server covers Metrica only

Example request

For the last 30 days show traffic sources and conversion for the Order checkout goal

MCP

Transport
stdio
Authentication
OAuth

Environment variables

YANDEX_METRIKA_TOKEN secret
A ready OAuth token with the metrika:read scope
YANDEX_METRIKA_COUNTER_ID
Default counter
ASKADS_TELEMETRY
0 disables anonymous telemetry

Limitations

Dedicated tools only read, but the generic request allows POST and DELETE, which run with `confirmWrite=true` and can change real Metrica objects. Confirmation depends on the AI app itself. By default the server sends anonymous telemetry to usage.gistrec.cloud: an instance ID, tool names and environment versions, with no token or arguments. It is switched off with ASKADS_TELEMETRY=0. Four stars, last commit in November 2026.

How to disable. Run the `logout` tool to delete the token from the computer, then remove the server from your client settings and revoke the app access in Yandex ID.

FAQ

Is a token needed in advance?

No, sign-in usually happens in chat through Yandex OAuth. A ready token goes into YANDEX_METRIKA_TOKEN for CI and non-standard setups.

Can the server change Metrica data?

Only through the generic request: POST and DELETE run with `confirmWrite=true`, and all other tools read.

Which Node.js version is needed?

Node.js 20 or newer; the server runs through npx with no separate install.

How do I switch off telemetry?

Set ASKADS_TELEMETRY=0; false, off and no are also accepted.

Where is the token stored?

In ~/.config/mcp-yandex-metrica/credentials.json with owner-only permissions.

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

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

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

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

README in short

The README moves from a sample dialogue to a quick start for Codex and other clients, and covers capabilities, mutating actions, connection, telemetry and limits, while docs holds documentation for each tool.

README badge

Report a problem