Hackle

Model Context Protocol server for Hackle
  • javascript

2

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "hackle-io-hackle-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@hackle-io/hackle-mcp@latest"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

You can connect to the Hackle MCP Server using an MCP client and your API key to query experiments, in-app messages, push messages, and time-series analytics. It provides structured access to data such as experiment lists, message details, data reports, analytics charts, and remote configs, enabling you to build dashboards and integrate Hackle data into downstream systems.

How to use

Connect to the Hackle MCP Server with your MCP client by configuring the server entry and providing your API key. You can fetch lists (experiments, in-app messages, push messages, data reports, remote configs) and retrieve detailed information for a specific item. You also have access to time-series data for active users, retention, and stickiness, as well as analytics charts for data insights and funnels. Use the tools to assemble dashboards, automate reports, and power data-driven decisions.

How to install

Prerequisites: you need Node.js and npm installed on your system.

  1. Install the MCP client via npx as shown in the example configuration.

  2. Create or update your MCP client configuration to run the Hackle MCP Server locally via npx and provide your API key.

  3. Restart your client application if it is running to apply the new MCP server configuration.

Follow the concrete steps below to enable the Hackle MCP Server in your environment.

Configuration and running the MCP server

Use the following configuration snippet to run the Hackle MCP Server with the MCP client. This example uses a local, stdio-based setup driven by npx.

{
  "mcpServers": {
    "hackle_mcp": {
      "command": "npx",
      "args": ["-y", "@hackle-io/hackle-mcp@latest"],
      "env": {
        "API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Installing in Claude client (example configuration)

Add the MCP server entry to Claude's desktop config so the client can locate and start the Hackle MCP Server. Here is an example entry you can adapt.

{
  "mcpServers": {
    "hackle-mcp": {
      "command": "npx",
      "args": ["-y", "@hackle-io/hackle-mcp@latest"],
      "env": {
        "API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Restart Claude after saving the file.

## Security and keys

Treat your API key as a sensitive credential. Do not share it or commit it to public repositories. Store it securely and rotate it if you suspect exposure.

## Troubleshooting tips

If the MCP server does not start, verify that your API\_KEY is set correctly and that the environment supports running npx. Check for network access if the remote server URL is used, and ensure the client has permission to reach Hackle endpoints.

## Available tools

### experiment-list

Fetches a paginated list of A/B test experiments with search functionality. Parameters: pageNumber, pageSize, searchKeyword.

### experiment-detail

Retrieves detailed information for a specific A/B test experiment. Parameters: experimentId.

### in-app-message-list

Fetches a paginated list of in-app messages with search functionality. Parameters: pageNumber, pageSize, searchKeyword.

### in-app-message-detail

Retrieves detailed information for a specific in-app message. Parameters: inAppMessageId.

### push-message-list

Fetches a paginated list of push messages with search functionality. Parameters: pageNumber, pageSize, searchKeyword.

### push-message-detail

Retrieves detailed information for a specific push message. Parameters: pushMessageId.

### active-user-series

Retrieves time-series data of active users. Available in daily, weekly, and monthly units. Parameters: unit, date.

### retention-series

Retrieves time-series data of user retention. Available in daily, weekly, and monthly units. Parameters: unit, date.

### stickiness-series

Retrieves time-series data of user stickiness (return visit frequency). Available in weekly and monthly units. Parameters: unit, date.

### data-report-list

Retrieves all data report metadata.

### data-report-detail

Retrieves a single data report's detail. Provides analytics chart id and type inside data report.

### analytics-chart-list

Retrieves data analytics chart's metadata list. Parameters: pageNumber, pageSize, searchKeyword, chartType.

### analytics-chart-detail

Retrieves data analytics chart's detail for visualization. Parameters: chartId, chartType.

### remote-config-list

Retrieves remote config list. Parameters: pageNumber, pageSize, searchKeyword, status.

### remote-config-detail

Retrieves remote config's detail. Parameters: remoteConfigId.

### remote-config-create

Creates an empty remote config with fields key, description, dataType, userIdentifierCriteria.

### remote-config-update

Updates remote config's content. Parameters: remoteConfigId, body with dataType, remoteConfigDefaultValue, conditionalValues, etc.

### remote-config-update-user-identifier-criteria

Updates remote config's user identifier criteria for production and development environments.

### remote-config-update-description

Updates remote config's description for production and development environments.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational