Aptabase MCP Server
OfficialRelated Servers
Alternatives to Aptabase MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceUnofficial MCP server that lets AI agents query Aptabase analytics using cookie-authenticated dashboard endpoints, providing tools for metrics, events, and sessions.171MIT
- AlicenseAqualityDmaintenanceFirst-party web analytics MCP server for AI agents, providing 42 tools to query traffic, events, funnels, conversions, sources, and performance data.4033 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to query PostHog analytics data directly via tool calls, including insights, events, feature flags, trends, and persons.525 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query Mixpanel event data, funnel conversion rates, and retention cohorts via MCP tools or natural language.392 npmMIT
- AlicenseBqualityAmaintenanceEnables 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.4319 npm4MIT
- AlicenseBqualityAmaintenanceEnables AI agents to query self-hosted product analytics, investigate changes with evidence and coverage checks, and use optional management tools for saved reports, goals, and keys.201MIT
TDQS
Scored across 17 tools
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.
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.
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.
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.