Skip to main content
Glama
key-arg

Statable Analytics

by key-arg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Statable Analytics

No user-submitted related servers found.

    Related Servers

    • Plausible Analytics MCP

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying privacy-focused website analytics from Plausible's read-only Stats API v2, with tools for overview, timeseries, breakdown, and goal performance metrics.
      20 npm
      MIT

    • plausible-mcp

      michldav
      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
      48 npm
      MIT

    • Cookie Free Analytics MCP

      PrestonsCreekCapital
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to cookieless web analytics aggregates such as sites, visitors, pages, sources, live activity, funnels, and uptime monitoring through OAuth 2.1-secured Streamable HTTP tools.
      MIT

    • Gizmo Analytics

      sudomichael
      A
      license
      A
      quality
      D
      maintenance
      Privacy friendly, cookieless web analytics built MCP-first. "Add analytics to my Next.js app" → an AI agent runs the setup_analytics_for_site tool, picks the right install snippet, edits your layout file, and verifies the script is loading. OAuth onboarding, no API keys to paste.
      28
      27 npm
      1
      MIT

    • @lodd/mcp-server

      hholen
      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
      33 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.7/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, with clear naming like top_pages vs top_countries and list_goals vs top_goals. The main overlap is query_stats, which can reproduce the top_* and visitors_over_time results, but the convenience tools are sufficiently specific that an agent can choose correctly.

    Naming Consistency5/5

    Tool names follow a consistent snake_case verb_noun pattern: list_*, get_*, create_*, update_*, top_*, plus a few descriptive exceptions like funnel_report and visitors_over_time. The conventions are predictable and readable throughout.

    Tool Count3/5

    25 tools is at the heavy end of the 16-25 range, and several tools could be consolidated, especially the top_* wrappers around query_stats. The count is defensible for a full analytics API, but it feels bloated rather than tightly scoped.

    Completeness2/5

    The set covers site creation, updates, stats queries, goals, funnels, and tracking settings, but there are no delete operations for sites, goals, or funnels, leaving obvious lifecycle gaps. Management workflows that require removing a site, goal, or funnel cannot be completed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources