Skip to main content
Glama
umami-compass

umami-compass

by webcredo

Related Servers

Alternatives to umami-compass

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for Umami analytics. It talks to the Umami REST API directly over HTTP, supporting self-hosted and cloud setups.
      8
      -
    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for Umami analytics, enabling natural language queries of website stats, traffic trends, events, sessions, and analytics reports.
      13
      1
      Elastic 2.0
    • A
      license
      A
      quality
      D
      maintenance
      A security-first MCP server for Umami analytics (Cloud and self-hosted v3) enabling analytics, reporting, and administration with least privilege and credential-safe design.
      32
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Umami Analytics that provides read-only tools to query website stats, events, sessions, reports, and more, enabling natural language analytics queries.
      12 npm
      3
      MIT

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target clearly distinct slices: site resolution/listing/metadata, aggregate stats, time series, ranked breakdowns, realtime, and date range are all separable. The analysis layer has mild overlap — explain_traffic_change, compare_traffic_series, and analyze_release_impact all perform period comparisons, and an agent could hesitate between them, though descriptions clarify (ranking vs. aligned buckets vs. release windows with CWV).

    Naming Consistency4/5

    Strong verb_noun snake_case pattern throughout (get_website_stats, list_websites, resolve_website, analyze_release_impact, compare_traffic_series). The only deviation is tracking_health_check, which is noun-first with no leading verb, but it remains readable and predictable in intent.

    Tool Count4/5

    15 tools sits at the top of the comfortable range for an analytics server and each has a defensible role. The higher-order analysis tools (release impact, traffic change, series comparison) do compose functionality already exposed by the base stats/metrics tools, which makes the set slightly heavier than strictly necessary.

    Completeness4/5

    Covers the read-only analytics lifecycle well: discovery (list/get/resolve), quantitative stats, series, dimension breakdowns, realtime, portfolio rollups, CWV, and health auditing, with sensible safety bounds and explicit truncation metadata. Gaps exist around session/event-level drill-down, saved reports or export, and any write operations (site creation, share links), but these are outside the apparent analysis-focused scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues