InnerVault

yandex-metrika-mcp

Stale Official MCP Registry, io.github.theYahia

MCP server for Yandex Metrika — web analytics, counters, goals, traffic (Russia)

Open the source (opens github.com) https://github.com/theyahia/yandex-metrika-mcp

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.

What it is

MCP servers from io.github.theYahia.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

@theyahia/yandex-metrika-mcp@2.1.1

From the server's entry in the official MCP Registry

Related

  1. Yandex Metrika MCP

    MCP servers

    Read-only Yandex Metrika MCP. Query visits, sources, geo, devices and more in plain language.

    Stale Official MCP Registry, io.github.expremiental Updated 4 months ago 1 note

  2. Yandex Metrika MCP

    MCP servers

    MCP server for Yandex Metrika API — web analytics, traffic, audience data

    Stale Official MCP Registry, io.github.stufently Updated 7 days ago 2 notes

    @stufently/yandex-metrika-mcp@2.3.0
  3. Полное покрытие API Яндекс Метрики: Stat, Management и Logs — 108 методов, 108 инструментов

    Stale Official MCP Registry, io.github.artgas1 Updated 2 months ago 2 notes

    yandex-metrika-mcp-server@3.3.1
  4. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  5. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  6. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0