Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Yandex Metrica MCP

by BoxLab-Ltdversion 1.0.1i★ 15iRuns on your computerRepository ↗
Registry nameio.github.BoxLab-Ltd/yandex-metrica-mcp

How to install

What it does

Query Yandex Metrica analytics — reports, trends, metadata and raw log exports — via an AI agent.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Marketing & social media

Use together with

Skills that teach the AI this kind of work; they work alongside this one

scroll-world

A skill that turn any brand into a scrollable 3D world landing page

by oso95★ 11,0651 skills

Skill · How-to guide

social-auto-upload

自动化上传视频到社交媒体:抖音、小红书、视频号、tiktok、youtube、bilibili

by dreammis★ 16,698 (whole repo)4 skills

Skill · How-to guide

native-subtitle-quote-image

保留视频内嵌字幕,精确取帧并生成 3:4 社交长图的 Agent Skill

by chengyi-ai★ 2,8911 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity23/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score35/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: 31 (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Yandex Metrica MCP. Follow https://mcp.popnx.com/i/boxlab-ltd-yandex-metrica-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yandex Metrica MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "yandex-metrica": { "command": "npx", "args": [ "-y", "yandex-metrica-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yandex Metrica MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "yandex-metrica": {
          "command": "npx",
          "args": [
            "-y",
            "yandex-metrica-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Yandex Metrica MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Yandex Metrica MCP or shows a Yandex Metrica MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • YANDEX_METRIKA_TOKEN Yandex Metrica OAuth token (metrika:read). Optional if you run the `auth` login.
  • YANDEX_METRIKA_COUNTER_ID Default counter id, so tools may omit counterId.
  • YANDEX_METRIKA_ENABLE_WRITE Set to 1 to add the write tools (chart annotations, expense upload). Sign-in then also asks for metrika:write; every change is confirmed.
  • YANDEX_METRIKA_LOGS_DIR Directory for Logs API file exports (logs_download in file mode). Defaults to a folder under the OS temp directory.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Yandex Metrica MCP yet

Yandex Metrica MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Yandex Metrica MCP

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Marketing & social media that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yandex Metrica MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user yandex-metrica -- npx -y yandex-metrica-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yandex Metrica MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user yandex-metrica -- npx -y yandex-metrica-mcp
  4. Type /mcp in Claude Code

    You should see Yandex Metrica MCP listed as connected

  5. Try it

    Use Yandex Metrica MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Yandex Metrica MCP or shows a Yandex Metrica MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • YANDEX_METRIKA_TOKEN Yandex Metrica OAuth token (metrika:read). Optional if you run the `auth` login.
  • YANDEX_METRIKA_COUNTER_ID Default counter id, so tools may omit counterId.
  • YANDEX_METRIKA_ENABLE_WRITE Set to 1 to add the write tools (chart annotations, expense upload). Sign-in then also asks for metrika:write; every change is confirmed.
  • YANDEX_METRIKA_LOGS_DIR Directory for Logs API file exports (logs_download in file mode). Defaults to a folder under the OS temp directory.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yandex Metrica MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "yandex-metrica": { "command": "npx", "args": [ "-y", "yandex-metrica-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yandex Metrica MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Yandex Metrica MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Yandex Metrica MCP or shows a Yandex Metrica MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • YANDEX_METRIKA_TOKEN Yandex Metrica OAuth token (metrika:read). Optional if you run the `auth` login.
  • YANDEX_METRIKA_COUNTER_ID Default counter id, so tools may omit counterId.
  • YANDEX_METRIKA_ENABLE_WRITE Set to 1 to add the write tools (chart annotations, expense upload). Sign-in then also asks for metrika:write; every change is confirmed.
  • YANDEX_METRIKA_LOGS_DIR Directory for Logs API file exports (logs_download in file mode). Defaults to a folder under the OS temp directory.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Yandex Metrica MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "yandex-metrica": { "type": "stdio", "command": "npx", "args": [ "-y", "yandex-metrica-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Yandex Metrica MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Yandex Metrica MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Yandex Metrica MCP or shows a Yandex Metrica MCP tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • YANDEX_METRIKA_TOKEN Yandex Metrica OAuth token (metrika:read). Optional if you run the `auth` login.
  • YANDEX_METRIKA_COUNTER_ID Default counter id, so tools may omit counterId.
  • YANDEX_METRIKA_ENABLE_WRITE Set to 1 to add the write tools (chart annotations, expense upload). Sign-in then also asks for metrika:write; every change is confirmed.
  • YANDEX_METRIKA_LOGS_DIR Directory for Logs API file exports (logs_download in file mode). Defaults to a folder under the OS temp directory.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Yandex Metrica MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user yandex-metrica -- npx -y yandex-metrica-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-metrica-mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "yandex-metrica-mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "yandex-metrica": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "yandex-metrica-mcp"
      ]
    }
  }
}

Values you fill in

  • YANDEX_METRIKA_TOKEN secret env
    Yandex Metrica OAuth token (metrika:read). Optional if you run the `auth` login.
  • YANDEX_METRIKA_COUNTER_ID env
    Default counter id, so tools may omit counterId.
  • YANDEX_METRIKA_ENABLE_WRITE env
    Set to 1 to add the write tools (chart annotations, expense upload). Sign-in then also asks for metrika:write; every change is confirmed.
  • YANDEX_METRIKA_LOGS_DIR env
    Directory for Logs API file exports (logs_download in file mode). Defaults to a folder under the OS temp directory.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
606/wk
Connection
Runs on your computer
Latest versioni
1.0.1
Published to registryi
Nov 6, 2026
Code last changedi
Nov 16, 2026
Maker
BoxLab-Ltd
Packages
npm: yandex-metrica-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account BoxLab-Ltd, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 4 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for yandex-metrica-mcp@1.0.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/boxlab-ltd-yandex-metrica-mcp.svg)](https://mcp.popnx.com/en/servers/boxlab-ltd-yandex-metrica-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Marketing & social mediai

  • More stars than 97% of the other 4225 servers in this category
  • Published to the registry more recently than 71% of the other 4225 servers in this category
  • Basic checks equal to or better than 99% of the other 4225 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Yandex Metrica MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 4 days ago, and the latest version (1.0.1) reached the registry 14 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

ChatbotX

Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.

by ChatbotXIOGrowing★ 1.1K Stars for the whole repoUpdated 14 days ago

Runs in the cloud✓ service owner · chatbotx.io

Betterlytics

Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.

by betterlyticsGrowing★ 196Updated 4 months ago

Runs in the cloud✓ service owner · betterlytics.io
Compared with similar ones
This one
Yandex Metrica MCP
RelaticleChatbotXX (Twitter) MCP Server by XquikBetterlyticsBibiGPT YouTube Video Summarizer
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoYesNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/44/44/4
LicenseMITAGPL-3.0NOASSERTIONMITAGPL-3.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

yandex-metrica-mcp

Ask your Yandex Metrica analytics in plain language — from Claude, Cursor, or any MCP client.

A Model Context Protocol (MCP) server for Yandex Metrica. It lets an AI agent query your web-analytics data — traffic, sources, landing pages, conversions, geography, devices and trends — through a small set of flexible, read-only tools — plus opt-in write tools that you confirm one change at a time.

Read-only by default, no secrets stored in the package: interactive login uses

a built-in public OAuth client with PKCE, and the server talks only to Yandex.

General-purpose: marketing, product analytics, e-commerce and SEO are all fair game — the server is not tied to any one use case.

Demo

Point an AI agent at your counter and ask about your traffic — the server queries Yandex Metrica and hands back real, read-only data, no dashboards. Here the run_report tool answers a “traffic sources, last 7 days” question against a live counter:

Quickstart

1. Add the server to your MCP client (e.g. Claude Desktop) — no token required up front; you log in interactively in step 2:

{

"mcpServers": { "yandex-metrica": { "command": "npx", "args": ["-y", "yandex-metrica-mcp"], "env": { "YANDEX_METRIKA_COUNTER_ID": "12345678" } } } }

2. Log in once — one command, no app registration, no secret stored:

npx yandex-metrica-mcp auth

Approve access in the browser and you're done — the code is handed back automatically over a local redirect, no copy-paste. The login uses authorization-code + PKCE, so no client secret ever touches your machine; the token is cached (mode 0600) and valid for ~1 year.

3. Ask your agent about traffic, sources, conversions, geography, devices, or trends — see Examples for prompts.

Prefer a static token (CI / non-interactive) or your own OAuth app? See Authentication.

Or install as a Claude Code plugin

The repo doubles as the plugin marketplace for BoxLab's Yandex MCP family, so you can install the server through Claude Code's plugin system instead of the config above:

/plugin marketplace add BoxLab-Ltd/yandex-metrica-mcp

/plugin install yandex-metrica-mcp@boxlab

Then sign in from the chat with the login tool (or run npx yandex-metrica-mcp auth). The same marketplace also carries yandex-webmaster-mcp. To turn on the write tools in the plugin, start Claude Code with YANDEX_METRIKA_ENABLE_WRITE=1 in the environment.

Or install as a Claude Desktop extension (.mcpb)

For a one-click install with no JSON, download the .mcpb from the latest release and open it with Claude Desktop (or drag it into Settings → Extensions). It asks for an optional default counter id; then sign in from the chat with the login tool (or run npx yandex-metrica-mcp auth).

Why

There is no official Yandex Metrica MCP server, and existing community ones are mostly thin, unmaintained, or dump raw data straight into the model's context. This server aims to be the well-engineered, well-maintained, open option: flexible report tools, strict token/context discipline, read-only by default.

Features

  • run_report — flexible wrapper over the Reporting API (/stat/v1/data).
  • run_comparison — compare two periods with absolute and percentage deltas.
  • run_drilldown — drill down through a dimension tree.
  • run_timeseries — metrics split into a time series (/bytime) for trends.
  • get_metadata — discover the counters on your account and a catalog of common dimensions/metrics (and Logs API fields) so the model queries with real names.
  • describe_counter — read one counter's configuration (goals, segments, filters, operations, access grants, chart annotations) via an include selector. The goals section gives the goal ids needed for conversion metrics in run_report.
  • logs_request / logs_status / logs_download / logs_clean — Logs API: export raw, un-sampled session (visits) or hit (hits) rows. Async lifecycle (request → poll → download → clean); logs_download returns a bounded sample inline by default, or streams the full export to a file — never dumping raw rows into the model's context.
  • login / submit_code — sign in to Yandex Metrica from your MCP client, no terminal needed: login opens the browser and captures the code over a local redirect, or hands back a URL and takes the pasted code via submit_code.
  • Built-in context control: field selection on by default, low default row limits, and sampling/quota surfaced back to the model.
  • Analysis hygiene: the server hands every client a short set of rules (exclude robots, compare complete periods, never sum users, use explicit goals, …). The Claude Code plugin adds the fuller metrica-hygiene skill.
Write tools (opt-in)

Off unless you set YANDEX_METRIKA_ENABLE_WRITE=1. Then the server adds:

  • manage_annotation — create, update or delete a note pinned to a chart date (a release, a campaign start, an outage).
  • upload_expenses — import ad costs from a non-Yandex source as CSV, so Metrica reports cost and ROI. dryRun: true validates the file and shows the rows, dates and totals without sending anything.

With the flag on, sign-in also asks for the metrika:write scope — run auth (or the login tool) once more after turning it on. Without the flag the sign-in asks for read access only, and tokens issued earlier keep working. Every change is confirmed by you before it is sent: your client shows a confirmation prompt if it supports MCP elicitation, otherwise the tool returns a summary and a one-time token that the agent can use only after you agree. The server also checks that your account has edit access to the counter.

Local HTTP mode

By default the server talks stdio, started by your MCP client. For clients that connect by URL, or to share one running server between several clients, start it over Streamable HTTP:

npx yandex-metrica-mcp --http            # http://127.0.0.1:7801/mcp

npx yandex-metrica-mcp --http --port 9000

Or set MCP_TRANSPORT=http (and MCP_HTTP_PORT). Every client gets its own session; they share one sign-in and one request budget. The server listens on 127.0.0.1 only and rejects requests whose Host or Origin is not local, so a web page cannot reach it. To listen on another interface (--host 0.0.0.0, e.g. in Docker) you must set MCP_HTTP_TOKEN; clients then send Authorization: Bearer . This is a local mode, not hosting: one user, one Yandex account.

Requirements

  • Node.js >= 18
  • Yandex Metrica credentials with the metrika:read scope (see Authentication), plus metrika:write for the opt-in write tools. Whoever the credentials belong to must have access to the counters you query.

Authentication

Recommended: interactive login. No app registration needed — the server ships a built-in public OAuth client. Run once:

yandex-metrica-mcp auth     # or, in dev: bun run auth

It opens the Yandex consent page in your browser; after you approve, the code is returned automatically over a loopback redirect (http://127.0.0.1:53682) — no copy-paste. If that port is taken, it falls back to showing a code you paste in (force that flow with auth --oob, or change the port with YANDEX_OAUTH_LOOPBACK_PORT). The token is cached at ~/.config/yandex-metrica-mcp/token.json (mode 0600) and is valid for ~1 year; re-run auth when it expires. The login uses authorization-code + PKCE, so no client secret is stored anywhere. A cached login takes precedence over YANDEX_METRIKA_TOKEN.

From your MCP client (no terminal). Not signed in yet? The server still starts — ask your agent to run the login tool and it does the same browser flow in-process (or returns a URL and takes the code via submit_code). Handy for GUI clients like Claude Desktop, where there is no terminal to run auth.

Static token. Get a token for an app with the metrika:read scope at https://oauth.yandex.ru and pass it as YANDEX_METRIKA_TOKEN — handy for CI or non-interactive use.

Own OAuth app (optional). To use your own app instead of the built-in one, set YANDEX_OAUTH_CLIENT_ID; add YANDEX_OAUTH_CLIENT_SECRET to also enable automatic token refresh.

Configuration

The Quickstart covers the happy path. For all options — static token, your own OAuth app, default counter, request tuning, language — see .env.example. The published package runs on Node (so npx/MCP clients work out of the box); local development uses Bun.

Examples

Once connected, an agent can answer questions like:

  • “How many visits and users did counter 12345678 get last week, split by traffic source?” → run_report with metrics: ["ym:s:visits","ym:s:users"], dimensions: ["ym:s:lastsignTrafficSource"].
  • “Compare this week's organic conversions to last week's.” → run_comparison (server returns A, B, and the deltas).
  • “Which operating systems do my visitors use? Let me drill into Windows versions.” → run_drilldown, then again with parentId.
  • “What counters do I have?” → get_metadata.
  • “List this counter's goals, then show how the ‘Purchase’ goal converted last week.” → describe_counter (include: ["goals"]) for the goal id, then run_report with ym:s:goal conversionRate.
  • “Export last month's raw sessions with landing pages and referrers for offline analysis.” → logs_request (source: "visits"), poll logs_status, then logs_download (mode: "file"), then logs_clean to free the quota.

Development

This project is Bun-first:

bun install

bun run dev # run from source with hot reload bun run typecheck # tsc --noEmit bun run lint # eslint bun test # bun's test runner bun run build # emit dist/ with tsc (Node-compatible)

The skill has an eval suite in evals/ that runs against mocked Metrica tools, so it never touches the real API:

claude plugin eval . --ablation none

License

MIT © boxlab