Skip to main content
Glama
mikusnuz

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to umami-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      18 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
      17 npm
      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
      17 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

    C2.9/5.0

    Scored across 66 tools

    Disambiguation2/5

    The main resource groups (websites, users, teams, reports) are clear, but the analytics getter cluster is dense: get_events, get_event_series, get_event_values, get_event_data_events/stats/fields/values, get_session_stats, get_session_data_properties/values, and get_sessions_weekly all overlap easily. An agent is likely to mis-select among these event/session property getters.

    Naming Consistency4/5

    Nearly all tools follow a consistent snake_case verb_noun pattern with sensible list/get/create/update/delete semantics. Minor outliers like heartbeat and batch_events slightly break the pattern, but the overall convention is readable and predictable.

    Tool Count1/5

    66 tools is far beyond the recommended 3-15 range and exceeds the 50+ threshold for an extreme tool count. Many analytics getters are highly granular and overlapping, making the surface feel over-decomposed rather than well-scoped.

    Completeness4/5

    The surface is nearly complete for Umami administration and analytics: websites, users, teams, reports, event ingestion, and read-only analytics are all covered with CRUD/lifecycle operations. Minor gaps such as share-link management and self-service team leave are workaround-able but not fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources