ya-metrics-mcp

Install

npx skillfoxx add mcp/ya-metrics-mcp

claude mcp add --transport stdio --env 'YANDEX_API_KEY=<your YANDEX_API_KEY>' ya-metrics -- uvx ya-metrics-mcp

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

code --add-mcp '{"name":"ya-metrics","type":"stdio","command":"uvx","args":["ya-metrics-mcp"],"env":{"YANDEX_API_KEY":"<your YANDEX_API_KEY>"}}'

{
  "servers": {
    "ya-metrics": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

codex mcp add ya-metrics --env 'YANDEX_API_KEY=<your YANDEX_API_KEY>' -- uvx ya-metrics-mcp

[mcp_servers.ya-metrics]
command = "uvx"
args = ["ya-metrics-mcp"]
env = { YANDEX_API_KEY = "<your YANDEX_API_KEY>" }

gemini mcp add -s user -e 'YANDEX_API_KEY=<your YANDEX_API_KEY>' ya-metrics uvx ya-metrics-mcp

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "mcp": {
    "ya-metrics": {
      "type": "local",
      "command": [
        "uvx",
        "ya-metrics-mcp"
      ],
      "environment": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "context_servers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": [
        "ya-metrics-mcp"
      ],
      "env": {
        "YANDEX_API_KEY": "<your YANDEX_API_KEY>"
      }
    }
  }
}

{
  "mcpServers": {
    "ya-metrics": {
      "command": "uvx",
      "args": ["ya-metrics-mcp"],
      "env": {
        "YANDEX_API_KEY": "your_oauth_token"
      }
    }
  }
}

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.

Example request

Compare mobile vs desktop users this month for counter 12345678

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.

MCP

Transport

stdio

Authentication

API key

Security check

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

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.

Related