hackle-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HACKLE_API_KEY | Yes | Your Hackle API key obtained from the Hackle team |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| experiment-listC | Fetches a paginated list of A/B test experiments with search functionality. |
| experiment-detailC | Retrieves detailed information for a specific A/B test experiment. |
| in-app-message-listC | Fetches a paginated list of in-app messages with search functionality. |
| in-app-message-detailC | Retrieves detailed information for a specific in-app message. |
| push-message-listC | Fetches a paginated list of push messages with search functionality. |
| push-message-detailC | Retrieves detailed information for a specific push message. |
| active-user-seriesB | Retrieves time-series data of active users. Available in daily, weekly, and monthly units. |
| retention-seriesC | Retrieves time-series data of user retention. Available in daily, weekly, and monthly units. |
| stickiness-seriesC | Retrieves time-series data of user stickiness (return visit frequency). Available in weekly and monthly units. |
| data-report-listC | fetch data report list. |
| data-report-detailC | fetch data report detail. |
| analytics-chart-listC | fetch data analytics chart list. |
| analytics-chart-detailC | fetch analytics chart detail. You can visualize the chart using this tool's result. |
| remote-config-listC | Fetch Remote Config list. |
| remote-config-detailC | Fetch remote config detail. |
| remote-config-createC | Creates an empty remote config. It is recommended to update an existing RC first if there is an associated RC with the one you want to create since the total number of RC is limited. |
| remote-config-updateC | Updates remote config's content. |
| remote-config-update-user-identifier-criteriaC | Updates remote config's user identifier criteria. The change will be applied to both production and development environment. |
| remote-config-update-descriptionC | Updates remote config's description. The change will be applied to both production and development environment. |
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 19 tools
Most tools have clear distinct purposes targeting specific resources like experiments, messages, remote configs, and analytics. However, there is some overlap between 'analytics-chart-detail' and 'data-report-detail' which could cause confusion as both fetch detail data for visualizations or reports, though they target different underlying data types.
Tool names follow a highly consistent pattern of 'resource-action' format using kebab-case throughout, such as 'experiment-list', 'remote-config-update', and 'active-user-series'. This predictability makes it easy for agents to understand and navigate the toolset.
With 19 tools, the count is slightly high but reasonable for an analytics and A/B testing platform covering multiple domains like experiments, messages, remote configs, and data reports. It might feel a bit heavy, but each tool appears to serve a specific function without obvious redundancy.
The toolset provides comprehensive CRUD and lifecycle coverage for its domains, including list and detail operations for experiments, messages, remote configs, and data reports, plus create and update tools for remote configs. The inclusion of time-series tools like 'active-user-series' and 'retention-series' adds analytical depth, leaving no obvious gaps for the server's purpose.