Skip to main content
Glama
rampstackco

@rampstack/umami-mcp

by rampstackco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @rampstack/umami-mcp

No user-submitted related servers found.

    Related Servers

    • @byterover/umami-mcp

      campfirein
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for Umami analytics, enabling natural language queries of website stats, traffic trends, events, sessions, and analytics reports.
      13
      5 npm
      1
      Elastic 2.0

    • umami-mcp-server

      frontedu
      A
      license
      Not graded
      quality
      C
      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

    • Umami MCP Server

      Mzaxd
      A
      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
      6 npm
      MIT

    • umami-mcp-server

      MurkyPuma
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that gives Claude read access to Umami web analytics, allowing natural language queries for stats, breakdowns, pageview trends, live visitors, and user journeys.
      10
      1
      MIT

    • umami-analytics-mcp

      matious89pl
      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
      6 npm
      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

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing websites, summary stats, pageview timeseries, top dimension values, custom event data, and a combined cohort report. Overlap is minimal and descriptions clarify boundaries.

    Naming Consistency4/5

    Most tools follow the 'verb_noun' pattern (list_websites, get_stats, get_pageviews, get_metrics, get_event_data), but 'cohort_report' breaks the pattern with a noun_noun format, causing a minor inconsistency.

    Tool Count5/5

    With 6 tools, the server is well-scoped for an analytics API. Each tool serves a distinct analysis need without redundancy or bloat.

    Completeness5/5

    The tool set covers all core analytics queries: listing websites, aggregate stats, timeseries pageviews, top metrics, event data, and a combined snapshot. No obvious gaps for read-only analytics.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources