Skip to main content
Glama
aptabase

Aptabase MCP Server

Official
by aptabase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Aptabase MCP Server

No user-submitted related servers found.

    Related Servers

    • aptabase-mcp

      billylo1
      A
      license
      A
      quality
      F
      maintenance
      Unofficial MCP server that lets AI agents query Aptabase analytics using cookie-authenticated dashboard endpoints, providing tools for metrics, events, and sessions.
      17
      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
      34 npm
      MIT

    • posthog-mcp

      johnnikolo
      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
      MIT

    • rybbit-mcp

      nks-hub
      A
      license
      A
      quality
      B
      maintenance
      Enables querying Rybbit Analytics data directly through MCP-compatible clients like Claude Code. It provides tools for monitoring website statistics, user sessions, error logs, funnels, and performance metrics via natural language.
      40
      13 npm
      4
      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

    B3.3/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools are clearly distinct, with specific query purposes like top countries vs top OS. However, some overlap exists between get_metrics and get_periodic_stats, and the many get_top_* variants could be confused without reading descriptions closely. Overall, descriptions help distinguish them.

    Naming Consistency4/5

    The vast majority follow a consistent get_<resource> pattern. The main deviation is list_apps instead of get_apps, which breaks the pattern slightly. All other tools use get_ consistently, making the naming predictable and readable.

    Tool Count3/5

    With 17 tools, the server sits in the heavy range (16-25). While each tool serves a distinct analytical purpose, the sheer number of top_* getters (12 variants) makes the surface feel somewhat bloated. A few could be combined into parameterized queries, but the count is not unreasonable for an analytics domain.

    Completeness4/5

    The tool surface covers a broad range of analytics needs: app management, live and historical sessions, metrics, time-series, geographic breakdowns, device/OS details, event properties, and usage counts. Minor gaps exist (e.g., no funnel or retention analysis), but for a read-only analytics MCP, it is quite comprehensive.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources