claude.ai Web & Desktop Integration

This guide explains how to connect Hackle MCP through a custom connector on the claude.ai web.

The process is the same for Claude Desktop.

Prerequisites

• A Claude account that can use custom connectors

  • Free plan: Can add up to one custom connector

  • Paid plan (Pro): No limit

  • Team / Enterprise: If the workspace administrator has disabled adding custom connectors, the menu itself will not be shown

• A Hackle API key — see https://docs.hackle.io/external-link/model-context-protocol for how to issue one

1. Open the connectors page

1. Log in to claude.ai.

2. In the left sidebar, click Settings → Connectors.

2. Add a custom connector

1. Click the + button in the top right of the connectors page and select Add custom connector. Go to page

2. Enter the following into the dialog that appears and click Add.

Name: Hackle
Remote MCP server URL: https://mcp.hackle.io/mcp

3. Enter your Hackle API key

After adding the URL, click the connect button to open the authentication screen. Paste your Hackle API key into the API key field and proceed.

4. (Optional) Review tool permissions

After connecting, click the Hackle connector on the connectors page to see the list of available tools and their permissions. If needed, you can adjust the settings to allow only certain tools.

5. Verify the connection

Open a new conversation and enter the following:

Tell me the available Hackle tools

If the response includes tool names such as experiment-list and in-app-message-list, the connection was successful.

FAQ

I don't see the "Add custom connector" menu.

One of the following may apply:

• On the free plan, if you are already using one other custom connector, adding more is restricted.

• On the Claude Team / Enterprise plan, if the administrator has disabled adding custom connectors, the menu itself will not be shown. Please contact your Claude plan administrator.

I want to switch to a different API key. On the connectors page, go to the Hackle item → Disconnect, then add it again to authenticate with the new key.

I want to view data from a different workspace. Currently API keys are issued per workspace, so to query a different workspace you need to reconnect with a new API key. In the future, this will be updated so that you can query multiple workspaces with a single API key.