Koskamo

Yandex Metrika MCP

An open-source MCP server that allows agents to query Yandex Metrika analytics in plain language. It supports read-only access to visits, sources, geo, devices, and more without requiring manual API key management or SQL queries.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Yandex Metrika MCP logo, by aiaiaiCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by aiaiai
MCP endpoint (Streamable HTTP)
https://mcp.getaiaiai.ru/yandex-metrika
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (2)

2 of 2 have a description · 0 of 2 declare behavior hints · 0 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Query weekly visit counts
  • Identify top traffic sources for a specific month
  • Check mobile traffic share for the current day

Source and maintenance

Community listingRegistry 0.1.0
mcp-registry: io.github.expremiental/yandex-metrika-mcp@0.1.0Source repository
Maintenance checked

Protocol and capabilities

Server
yandex-metrika-mcp 3.4.8
MCP protocol negotiated in check
2025-11-25
Tools
2 advertised
Resources
0 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "logging": {},
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "subscribe": false,
    "listChanged": true
  },
  "extensions": {
    "io.modelcontextprotocol/ui": {}
  },
  "experimental": {}
}

Tools

2 advertised

list_counters
Advertised by the server during the last successful anonymous check.

List Yandex Metrika counters available to the token. Returns each counter's id, name and site so you can pick a `counter_id` for `query`. Read scope is enough.

list_counters input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
list_counters output schema
{
  "type": "object",
  "required": [
    "result"
  ],
  "properties": {
    "result": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": true
      }
    }
  },
  "x-fastmcp-wrap-result": true
}
query
Advertised by the server during the last successful anonymous check.

Run a Reporting API query against a Metrika counter (aggregated stats). Pass Metrika field names directly. Common ones: Metrics (comma-separated): ym:s:visits, ym:s:users, ym:s:pageviews, ym:s:bounceRate, ym:s:avgVisitDurationSeconds, ym:s:newUsers Dimensions (comma-separated, optional — groups the result): ym:s:date, ym:s:lastTrafficSource, ym:s:startURL, ym:s:deviceCategory, ym:s:regionCountry, ym:s:<attribution>UTMSource date1 / date2: YYYY-MM-DD or relative (today, yesterday, NdaysAgo). filters: Metrika filter expression, e.g. "ym:s:deviceCategory=='mobile'". sort: field to sort by; prefix with '-' for descending, e.g. "-ym:s:visits". Returns the raw Reporting API response (query meta, totals and data rows).

query input schema
{
  "type": "object",
  "required": [
    "counter_id",
    "metrics"
  ],
  "properties": {
    "sort": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "date1": {
      "type": "string",
      "default": "7daysAgo"
    },
    "date2": {
      "type": "string",
      "default": "today"
    },
    "limit": {
      "type": "integer",
      "default": 100
    },
    "filters": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "metrics": {
      "type": "string"
    },
    "counter_id": {
      "type": "integer"
    },
    "dimensions": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
query output schema
{
  "type": "object",
  "additionalProperties": true
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-06: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
954 ms
95th percentile latency
954 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 954 ms · metadata changed · 2 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http yandex-metrika-mcp-getaiaiai https://mcp.getaiaiai.ru/yandex-metrika

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add yandex-metrika-mcp-getaiaiai --url https://mcp.getaiaiai.ru/yandex-metrika

Cursor

Merge this server into .cursor/mcp.json in your project, then enable yandex-metrika-mcp-getaiaiai in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "yandex-metrika-mcp-getaiaiai": {
      "url": "https://mcp.getaiaiai.ru/yandex-metrika"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "yandex-metrika-mcp-getaiaiai": {
      "type": "streamableHttp",
      "url": "https://mcp.getaiaiai.ru/yandex-metrika",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start yandex-metrika-mcp-getaiaiai and inspect its tools.
VS Code configuration
{
  "servers": {
    "yandex-metrika-mcp-getaiaiai": {
      "type": "http",
      "url": "https://mcp.getaiaiai.ru/yandex-metrika"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http yandex-metrika-mcp-getaiaiai https://mcp.getaiaiai.ru/yandex-metrika

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.getaiaiai.ru/yandex-metrika

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "yandex-metrika-mcp-getaiaiai": {
      "serverUrl": "https://mcp.getaiaiai.ru/yandex-metrika"
    }
  }
}

Let your agent find its tools

Find servers like Yandex Metrika MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,552