Yandex Metrika MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    const child = spawn(command, args, { stdio: "ignore", detached: true });

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.

    const child = spawn(command, args, { stdio: "ignore", detached: true });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

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 yandex-metrika-mcp -- npx -y @dev-crabs/yandex-metrika-mcp

{
  "mcpServers": {
    "yandex-metrika-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dev-crabs/yandex-metrika-mcp"
      ]
    }
  }
}

[mcp_servers.yandex-metrika-mcp]
command = "npx"
args = ["-y", "@dev-crabs/yandex-metrika-mcp"]

{
  "mcpServers": {
    "yandex-metrika-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dev-crabs/yandex-metrika-mcp"
      ]
    }
  }
}

{
  "servers": {
    "yandex-metrika-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@dev-crabs/yandex-metrika-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: YM_MCP_CLIENT_ID (Optional: your own Yandex OAuth app client ID (public PKCE client, no secret)), YANDEX_METRIKA_TOKEN (Optional: an existing OAuth token with metrika:read, for headless setups).