Skip to main content
Glama
Sign In
Yandex Metrika MCP

Yandex Metrika MCP

by DevCrabs-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Yandex Metrika MCP

No user-submitted related servers found.

    Related Servers

    • Google Analytics MCP Server

      rinaldofesta
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Google Analytics 4 data using natural language through MCP clients like Claude and Cursor, supporting 200+ dimensions and metrics for traffic, user behavior, and e-commerce analysis.
      MIT

    • Google Analytics MCP Server

      surendranb
      A
      license
      A
      quality
      B
      maintenance
      Connects Google Analytics 4 data to Claude, Cursor and other MCP clients, enabling natural language queries of website traffic, user behavior, and analytics data with access to 200+ GA4 dimensions and metrics.
      12
      1,117 PyPI
      244
      MIT

    • GA4 MCP Server

      luminarylane
      A
      license
      A
      quality
      C
      maintenance
      Connects MCP clients like Claude Desktop to Google Analytics 4 Data API, enabling natural language queries for reports, top pages, traffic sources, conversions, realtime users, and period comparisons.
      7
      MIT

    • lookout-mcp

      lookoutstats
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients such as Claude and Cursor to query Vercel Web Analytics across all your projects, covering visitors, sources, campaigns, Core Web Vitals, cross-site traffic, alerts and exportable board reports. It also supports annotations, resources and guided prompts for weekly briefs and traffic-drop investigations via a hosted or local server.
      82 npm
      MIT
    • Logly MCP server

      Logly MCP serverofficial

      logly-uk
      A
      license
      A
      quality
      C
      maintenance
      Query your Logly web analytics — traffic, breakdowns, funnels, real-time visitors — from Claude, Cursor or any MCP client.
      8
      57 npm
      2
      MIT

    • GA4 MCP

      tagpilot
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Claude and Cursor to run read-only Google Analytics 4 queries — reports, funnels, realtime data, property and stream setup, custom dimensions, plus tracking-health checks for duplicate transactions and traffic attribution — with a one-time browser Google sign-in and no Google Cloud project required. GA4 data flows directly from the local machine to Google, and only read-only analytics access is requested.
      Apache 2.0
    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.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: connection lifecycle, counter discovery/settings, catalog lookup, one-period reports, timeseries, period comparison, export jobs, and artifact reading. The potentially overlapping reporting tools (run_report, run_timeseries, compare_periods) are well differentiated by timeframe and output shape. An agent can reliably select the correct tool without guessing.

    Naming Consistency4/5

    All tools share the metrika_ prefix and lowercase snake_case, which is highly consistent. Most names follow a verb_noun pattern, but status and catalog are noun-style and connect/disconnect lack a noun object, so it falls just short of a strict uniform pattern. Still, the convention is predictable and readable.

    Tool Count5/5

    Thirteen tools is well within the comfortable range and each tool earns its place. The set cleanly separates authentication, discovery, reporting, comparison, timeseries, and export/job workflows. There are no redundant or filler tools.

    Completeness5/5

    The surface covers the full read-only analytics lifecycle: connect/disconnect/status, list and describe counters, inspect available fields, run flexible reports and timeseries, compare periods, export large results, poll/cancel jobs, and read artifacts. There are no obvious dead ends for the stated Yandex Metrika reporting purpose. Write/admin operations are intentionally excluded by read-only access, which is coherent with the design.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources