Claude Code Integration

This guide explains how to connect Hackle MCP in Claude Code, Anthropic's official CLI.

Prerequisites

• The latest version of Claude Code

• A Hackle API key — see MCP(Model Context Protocol) for how to issue one

Method A — Add via the authentication flow (recommended)

When you renew your API key in the future, you can handle it by re-authenticating.

1. Register the MCP server

claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcp

By default, it is registered only locally for the current project. To use it across all projects:

claude mcp add --transport http --scope user hackle-mcp https://mcp.hackle.io/mcp

2. Trigger authentication

Inside a Claude Code session:

/mcp

You will see an indication next to hackle-mcp that authentication is required. Selecting the item opens the browser and displays the Hackle authentication screen. Paste your Hackle API key into the API key field and proceed.

3. Verify the connection

/mcp

When hackle-mcp shows a status of connected, you're done. You can use the tools in a new prompt.

Method B — Embed the API key directly in the header

For quick setup, you can specify the header directly. Since the API key is stored in plain text in the config file, we recommend using this only in your personal environment.

claude mcp add --transport http hackle-mcp https://mcp.hackle.io/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

In this case, you can use the tools immediately without a separate authentication step.

Management commands

claude mcp list              # List registered servers
claude mcp get hackle-mcp    # Details
claude mcp remove hackle-mcp # Remove

Within a session, you can check the status and re-authenticate with the /mcp command.

Migrating from a local server

If you have been using an existing local MCP server (the npm package form) registered in Claude Code, you can follow these steps to move to the remote server.

1. Remove the existing local server

claude mcp list                          # Check the registered name
claude mcp remove hackle-mcp             # Change accordingly if the name is different

2. Register the remote server

Register by following Method A or Method B above. You can use the same API key value you were using before.

3. Clean up the local server package (optional)

If you have a globally installed npm package, remove it.

npm uninstall -g @hackle-io/hackle-mcp