Skip to main content
Glama
yandex-metrika-mcp

yandex-metrika-mcp

by expremiental

Related Servers

Alternatives to yandex-metrika-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to retrieve comprehensive analytics data from Yandex Metrika accounts, including traffic, content, e-commerce, and user demographics.
      113 npm
      1
      MIT
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to query Yandex Metrika traffic stats, Webmaster search performance and indexing, Direct ad spend reports, and Wordstat keyword frequencies through natural language. It is read-only except for confirmed page recrawl requests, runs locally with no third-party dependencies, and keeps OAuth tokens in the OS keychain.
      15
      34 PyPI
      4
      MIT
    • 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
      195 npm
      4
      MIT
    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language querying of Google Analytics 4, including reports, realtime data, custom dimensions, and property management.
      127 npm
      MIT

    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