Skip to main content
Glama

Related Servers

Alternatives to Metricairn

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to query a privacy-focused analytics service for aggregate stats, breakdowns, realtime visitors, and time-series trends across cloud or self-hosted deployments. It also provides connectivity checks and guided analytics playbooks.
      8
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to query PostHog analytics data directly via tool calls, including insights, events, feature flags, trends, and persons.
      5
      29 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      First-party web analytics MCP server for AI agents, providing 42 tools to query traffic, events, funnels, conversions, sources, and performance data.
      40
      11 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to explore a project's captured events and properties, then run trend, funnel and retention analyses and create or list saved insights. Tools are model-oriented, returning trimmed, budgeted results and actionable errors, with the project resolved from the API key or bearer token rather than passed as an argument.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI tools that support the Model Context Protocol to query Plausible Analytics traffic and conversion data, break metrics down by page, source, country, device, and UTM parameters, and compare two date ranges side by side. All query tools are read-only and work with either a hosted bring-your-own-key endpoint or a local STDIO install.
      4
      33 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 20 tools

    Disambiguation3/5

    Several tools overlap in querying and comparison capabilities, notably query_metrics vs run_query vs ask, and compare vs investigate_change vs detect_anomalies. Descriptions do clarify intended use, but an agent must read carefully to avoid misselection. Distinct areas like realtime, notes, health, and usage are clearer.

    Naming Consistency3/5

    All names use lowercase snake_case, but the pattern is inconsistent: list_, get_, query_, run_, bare verbs like compare/ask/detect_anomalies, and noun phrases ending in _report. It remains readable but lacks a single predictable verb_noun convention.

    Tool Count3/5

    At 20 tools, the server sits at the heavy end of the reasonable range for an analytics MCP. Many specialized reports justify their place, but the overlap among query and comparison tools suggests some consolidation is possible.

    Completeness4/5

    The surface broadly covers read-oriented analytics: discovery, queries, breakdowns, funnels, revenue, goals, retention, anomalies, investigations, health, realtime, and notes. Minor gaps remain, such as no tool to create/update timeline notes and no list_funnels to discover funnel names/IDs for funnel_report.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues