Yandex Metrika MCP

Install

{
  "mcpServers": {
    "yandex-metrika-mcp": {
      "command": "node",
      "args": [
        "{path-to-repo}/build/index.js"
      ],
      "env": {
        "YANDEX_API_KEY": "your_yandex_api_token_here"
      }
    }
  }
}

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

What it does

The server hands the agent ready-made Metrika reports instead of hand-built API queries. It covers visits for a period, source and traffic type summaries, search phrases and search engines, and new users by source. Other tools return content analytics by article, author and topic, demographics, devices, regions, goal conversion and page performance. Data can be grouped by day, week or month, and bounce rate is available for Yandex Direct experiments.

Who it is for. For marketers and analysts who check Metrika reports regularly and want to ask about traffic in plain language.

Example request

Show traffic sources for the last 7 days and which of them bring the most new users

Limitations

It needs a Metrika OAuth token issued through your own app at oauth.yandex.ru. The package is not on npm, so the server runs from a repository clone. The report set is fixed. The last commit is not recent, so check compatibility with the current API.

How to disable. Delete the yandex-metrika-mcp block from the MCP client config and revoke the token in Yandex ID settings if needed.

MCP

Transport

stdio

Authentication

API key

Security check

• Requires a Yandex account OAuth token
• Sends site statistics into the agent context

README in short

The README lists server capabilities by report group and gives an MCP config snippet that runs build/index.js with node. It explains in detail how to create an app at oauth.yandex.ru, which scopes to pick and how to get a token. It then lists every tool with a short purpose and the requirements: Node.js 18 and a Metrika API token. MIT license.

Related