# SEO Tools: Yandex.Metrica MCP server

> Read Yandex.Metrica traffic, goals, geo, device and search phrase reports through the Stat API, read-only.

- Listing: https://mcp.tc/i/seo-tools-yandex-metrica
- Connect: this is a local (stdio) server; install it on your machine (see Install). The listing link is a page, not an MCP endpoint.
- Type: local (stdio)
- Auth: API key
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: antohins
- Repository: <https://github.com/antohins/seo-tools-mcp>
- Package: npm `seo-tools-mcp-metrika`

## About

Connects to the Yandex.Metrica Stat API and returns strict JSON reports. The metrika server in the seo-tools-mcp project lists counters and goals, and builds reports on traffic sources, geography, devices, landing page behavior, search phrases and top landing pages. All tools are read-only and change nothing in your account.

It runs locally over stdio through npx (seo-tools-mcp-metrika). It needs a Yandex OAuth token (YANDEX\_OAUTH\_TOKEN), or you can sign in interactively with an OAuth app client ID and secret, which supports token refresh. A default counter ID can be set with METRIKA\_COUNTER\_ID.

## What it can do

- List Yandex.Metrica counters and goals
- Run custom Stat API reports
- Break down traffic by time period
- Analyze traffic sources, geography and devices
- Review landing page behavior and top landings
- Get search phrase data

## Example prompts

- "List my Yandex.Metrica counters and their goals"
- "Show traffic sources for counter 12345 over the last 30 days"
- "Which landing pages had the most visits last week?"
- "Break down visits by device type for my main counter"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport stdio seo-tools-yandex-metrica --env "YANDEX_OAUTH_TOKEN=<YOUR_YANDEX_OAUTH_TOKEN>" --env "METRIKA_OAUTH_TOKEN=<YOUR_METRIKA_OAUTH_TOKEN>" --env "YANDEX_CLIENT_SECRET=<YOUR_YANDEX_CLIENT_SECRET>" -- npx -y seo-tools-mcp-metrika
```

2. Start Claude Code and type `/mcp`. **seo-tools-yandex-metrica** should show as connected.

Add `--scope user` to make it available in every project. Replace the placeholders with your own values.

### Claude Desktop

1. Open **Settings → Developer → Edit Config**. It opens `claude_desktop_config.json`. Add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "seo-tools-yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-metrika"
      ],
      "env": {
        "YANDEX_OAUTH_TOKEN": "<YOUR_YANDEX_OAUTH_TOKEN>",
        "METRIKA_OAUTH_TOKEN": "<YOUR_METRIKA_OAUTH_TOKEN>",
        "YANDEX_CLIENT_SECRET": "<YOUR_YANDEX_CLIENT_SECRET>"
      }
    }
  }
}
```

2. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in `~/Library/Application Support/Claude/` on macOS and `%APPDATA%\Claude\` on Windows.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=seo-tools-yandex-metrica&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsInNlby10b29scy1tY3AtbWV0cmlrYSJdLCJlbnYiOnsiWUFOREVYX09BVVRIX1RPS0VOIjoiPFlPVVJfWUFOREVYX09BVVRIX1RPS0VOPiIsIk1FVFJJS0FfT0FVVEhfVE9LRU4iOiI8WU9VUl9NRVRSSUtBX09BVVRIX1RPS0VOPiIsIllBTkRFWF9DTElFTlRfU0VDUkVUIjoiPFlPVVJfWUFOREVYX0NMSUVOVF9TRUNSRVQ%2BIn19>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "seo-tools-yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-metrika"
      ],
      "env": {
        "YANDEX_OAUTH_TOKEN": "<YOUR_YANDEX_OAUTH_TOKEN>",
        "METRIKA_OAUTH_TOKEN": "<YOUR_METRIKA_OAUTH_TOKEN>",
        "YANDEX_CLIENT_SECRET": "<YOUR_YANDEX_CLIENT_SECRET>"
      }
    }
  }
}
```

Needs Node.js on your computer. Replace the placeholders with your own values.

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the secret the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "seo-tools-yandex-metrica": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-metrika"
      ],
      "env": {
        "YANDEX_OAUTH_TOKEN": "${input:yandex-oauth-token}",
        "METRIKA_OAUTH_TOKEN": "${input:metrika-oauth-token}",
        "YANDEX_CLIENT_SECRET": "${input:yandex-client-secret}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "yandex-oauth-token",
      "description": "YANDEX_OAUTH_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "metrika-oauth-token",
      "description": "METRIKA_OAUTH_TOKEN",
      "password": true
    },
    {
      "type": "promptString",
      "id": "yandex-client-secret",
      "description": "YANDEX_CLIENT_SECRET",
      "password": true
    }
  ]
}
```

Needs Node.js on your computer.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "seo-tools-yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-metrika"
      ],
      "env": {
        "YANDEX_OAUTH_TOKEN": "<YOUR_YANDEX_OAUTH_TOKEN>",
        "METRIKA_OAUTH_TOKEN": "<YOUR_METRIKA_OAUTH_TOKEN>",
        "YANDEX_CLIENT_SECRET": "<YOUR_YANDEX_CLIENT_SECRET>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

### Codex

```bash
codex mcp add seo-tools-yandex-metrica --env "YANDEX_OAUTH_TOKEN=<YOUR_YANDEX_OAUTH_TOKEN>" --env "METRIKA_OAUTH_TOKEN=<YOUR_METRIKA_OAUTH_TOKEN>" --env "YANDEX_CLIENT_SECRET=<YOUR_YANDEX_CLIENT_SECRET>" -- npx -y seo-tools-mcp-metrika
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.seo-tools-yandex-metrica]
command = "npx"
args = ["-y", "seo-tools-mcp-metrika"]
env = { YANDEX_OAUTH_TOKEN = "<YOUR_YANDEX_OAUTH_TOKEN>", METRIKA_OAUTH_TOKEN = "<YOUR_METRIKA_OAUTH_TOKEN>", YANDEX_CLIENT_SECRET = "<YOUR_YANDEX_CLIENT_SECRET>" }
```

Needs Node.js on your computer. Replace the placeholders with your own values.

### Gemini CLI

```bash
gemini mcp add -e "YANDEX_OAUTH_TOKEN=<YOUR_YANDEX_OAUTH_TOKEN>" -e "METRIKA_OAUTH_TOKEN=<YOUR_METRIKA_OAUTH_TOKEN>" -e "YANDEX_CLIENT_SECRET=<YOUR_YANDEX_CLIENT_SECRET>" seo-tools-yandex-metrica npx -- -y seo-tools-mcp-metrika
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients that start local servers accept this shape:

```json
{
  "mcpServers": {
    "seo-tools-yandex-metrica": {
      "command": "npx",
      "args": [
        "-y",
        "seo-tools-mcp-metrika"
      ],
      "env": {
        "YANDEX_OAUTH_TOKEN": "<YOUR_YANDEX_OAUTH_TOKEN>",
        "METRIKA_OAUTH_TOKEN": "<YOUR_METRIKA_OAUTH_TOKEN>",
        "YANDEX_CLIENT_SECRET": "<YOUR_YANDEX_CLIENT_SECRET>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings, with the same `command`, `args` and `env` fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

## Recent changes

- 2026-10-06 21:21 UTC: Tracking started: version 1.8.0. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/seo-tools-yandex-metrica#history (Atom feed: https://mcp.tc/i/seo-tools-yandex-metrica/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.8.0
- Last checked: 2026-10-05
- Listed: 2026-10-05
- Updated: 2026-10-05

---
Source: https://mcp.tc/i/seo-tools-yandex-metrica (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
