Skip to main content
Glama
expremiental

yandex-metrika-mcp

by expremiental
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to yandex-metrika-mcp

No user-submitted related servers found.

    Related Servers

    • yandex-metrika-mcp

      IlyaVorozhbit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to retrieve comprehensive analytics data from Yandex Metrika accounts, including traffic, content, e-commerce, and user demographics.
      69 npm
      1
      MIT

    • Plausible MCP

      The-Focus-AI
      A
      license
      B
      quality
      D
      maintenance
      Enables natural language interaction with Plausible Analytics data to query traffic, visitors, engagement, and more using conversational questions.
      4
      1
      MIT

    • Yandex Metrica MCP

      askads
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Yandex Metrica analytics: query web analytics metrics, goals, conversions, and raw API data using natural language from AI clients like Claude and Cursor.
      8
      75 npm
      3
      MIT

    • analytics-mcp

      geadlydrim
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Google Analytics data via natural language, providing tools for account and property insights, core reports, funnels, realtime reports, and custom dimensions/metrics.
      Apache 2.0

    • mcp-ga4

      mharnett
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language querying of Google Analytics 4, including reports, realtime data, custom dimensions, and property management.
      93 npm
      MIT

    • yandex-mcp

      webkoth
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to work with Yandex Webmaster, Direct, and Metrika data through natural language, including managing sites, sitemaps, recrawls, ad campaigns with write-safety guards, and pulling traffic, conversion, and ad statistics.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly non-overlapping purposes: one discovers available counters, the other runs queries against a specific counter. An agent can easily choose the right tool.

    Naming Consistency4/5

    list_counters follows a verb_noun pattern while query is a bare verb, which is a minor inconsistency. However, both are concise and readable, and the query description clarifies its role.

    Tool Count3/5

    With only two tools, the server is minimal but not unreasonable for a read-only analytics API wrapper. It is serviceable yet feels slightly thin compared to more complete analytics integrations.

    Completeness4/5

    The pair covers the core workflow: list counters to obtain an ID, then query reporting data from that counter. Missing capabilities like retrieving counter metadata or metadata schemas are minor gaps for this read-only domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources