Aptabase MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APTABASE_BASE_URL | Yes | Base URL of the Aptabase instance. Use https://us.aptabase.com for US cloud, https://eu.aptabase.com for EU cloud, or your self-hosted URL (no trailing slash). | |
| APTABASE_AUTH_SESSION | Yes | Authentication session cookie value (auth-session) from the Aptabase dashboard. Required for API access; keep secret. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_appsA | List Aptabase apps available to the authenticated account (id, name, appKey, ownership). |
| get_appA | Get a single Aptabase app by id. |
| get_metricsA | Key metrics for an app over a period: daily users, sessions, events, avg duration. Includes previous-period comparison when a date range is set. |
| get_periodic_statsA | Time-series stats (users, sessions, events) bucketed by hour/day/month for charts. |
| get_top_eventsB | Top event names by total event count for the period. |
| get_top_countriesC | Top countries by unique sessions for the period. |
| get_top_osB | Top operating systems by unique sessions for the period. |
| get_top_os_versionsB | Top OS versions by unique sessions for the period. |
| get_top_app_versionsB | Top app versions by unique sessions for the period. |
| get_top_devicesB | Top device models by unique sessions for the period. |
| get_top_regionsC | Top regions by unique sessions for the period. |
| get_event_propsC | Breakdown of custom string/numeric properties for a specific event name. Requires eventName. |
| get_live_sessionsB | Recent/live sessions currently active for an app. |
| get_live_geoC | Live geographic distribution of current users for an app. |
| get_session_detailsA | Session timeline details (events, props, device/geo metadata) for a session id. |
| get_historical_sessionsC | Historical sessions for an app over a period, with optional filters. |
| get_monthly_usageB | Monthly event usage counts for billing/quota (year, month, events). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.