Yandex Metrica MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 1 734 installs a week from npm. Last commit 1 Nov 2026.
MCP server for Yandex Metrica API: list counters, goals and pull web-analytics statistics.
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
/(?<key>(?:login|password|secret|token|api[_-]?key|authorization)\s*[:=]\s*["']?|(?:bearer|basic)\s+)(?<val>[^,;]+)|[^\s,;]*(?:@|:\/\/|%3A|\p{L}\.\p{L})[^\s,;]*|(?<key2>\b(?:token|secret|password|api[_-]?key|access_token|refresh_token|client_secret)\s+)(?!(?:expired|invalid|is|…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-yandex-metrica -- npx -y mcp-yandex-metrica
{
"mcpServers": {
"mcp-yandex-metrica": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-metrica"
]
}
}
}
[mcp_servers.mcp-yandex-metrica]
command = "npx"
args = ["-y", "mcp-yandex-metrica"]
{
"mcpServers": {
"mcp-yandex-metrica": {
"command": "npx",
"args": [
"-y",
"mcp-yandex-metrica"
]
}
}
}
{
"servers": {
"mcp-yandex-metrica": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-yandex-metrica"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
YANDEX_METRIKA_TOKEN (Yandex Metrica OAuth token (scope metrika:read) — read access to analytics data. Treat it as a secret. Optional: without it the server starts anyway and connects through the in-chat login (start_login / finish_login)), YANDEX_METRIKA_OAUTH_CLIENT_ID (ClientID of your own Yandex OAuth app for the in-chat login. Defaults to the Ask Ads app scoped to metrika:read), YANDEX_METRIKA_COUNTER_ID (Default Metrica counter id, used when a tool call omits counterId), YANDEX_METRIKA_LANG (Language for API responses (ru, en, ...)), YANDEX_METRIKA_API_BASE (API root host. Override only for a proxy or a non-default endpoint), YANDEX_METRIKA_TIMEOUT_MS (Per-request timeout in milliseconds), YANDEX_METRIKA_MAX_RETRIES (Max retries for transient errors (429 rate limit, 5xx on reads)).
MCP server for Yandex Metrika API — counters, goals, reports, segments, logs
Yandex Metrica for AI agents: counters, goals, Reporting API and Logs API export over stdio.
MCP server for Yandex.Metrica Stat API (read-only).
Stdio MCP server for PromptEden projects, monitors, answers, and analytics.
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
MCP Server for VictoriaMetrics. Provides integration with VictoriaMetrics API and documentation
An MCP server for analyzing startup financial health and generating metrics reports locally.
MCP server for Google Lighthouse performance metrics
Answers built from our own checks of this server.