Migrating from a Local Server

The local MCP server is no longer updated, and support will end within the second half of 2026. Please follow this guide to complete your migration.

Does moving to the remote server send data outside? The remote server runs on Hackle infrastructure. Requests from your AI client query and respond with Workspace data through the Hackle MCP server, without going through any separate external system.

If you have been using the local MCP server (as an npm package), you can follow this guide to move to the remote server.

Why should you migrate?

• No installation or updates required. You are freed from managing npm packages, Node.js versions, and dependency conflicts.

• New tools are added only to the remote server. Recent tools such as CRM statistics analysis are not available on the local server.

• Always up to date. Server-side improvements and bug fixes apply immediately, with no client update required.

Key changes

You add the remote server through the custom connector UI inside the client. It is not done by writing command / args in claude_desktop_config.json as with the local server, and adding a url key in that same file does not work either.

Item	Local Server	Remote Server
How to add	Register command / args / env under mcpServers in claude_desktop_config.json	The client's Add custom connector UI
API key location	Environment variable (env.API_KEY)	Entered in the client's authentication screen

Migration steps

1

Issue a new MCP key

The API key you used with the local server cannot access some features of the remote server. You can request a new API key from the MCP Integration menu in the Hackle Dashboard.

2

Remove the existing local server configuration (Claude Desktop)

Claude Desktop -> Settings -> Developer -> Edit Config

• Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

• Linux: ~/.config/Claude/claude_desktop_config.json

Open the claude_desktop_config.json file in a text editor and remove the local Hackle server entry.

Before — Local Server:

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

Delete the hackle-mcp entry above and save. If there are other servers in the mcpServers object, keep them.

After — Local Server:

{
  "mcpServers": {
    
  }
}

3

Add the remote server as a connector

• Left sidebar Customize → Connectors → + → Add custom connector → remote MCP server URL https://mcp.hackle.io/mcp → enter your Hackle API key on the authentication screen.

• For detailed steps, see claude.ai Web Integration.

• Connect directly

4

Verify the integration

In a new conversation, try entering the message below.

Tell me the available Hackle tools

If the response includes tool names, your migration is complete.

5

Clean up the local server package (optional)

If you installed the npm package globally, remove it.

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

If you ran it with npx -y, clearing the cache is enough.

npx clear-npx-cache

6

Tool compatibility

The remote server includes all tools from the local server, with new domains added.

You can keep using your existing prompts. Tool names have not changed.

Domain	Local Server	Remote Server
Experiment (A/B Test)	✅	✅
In-App Message	✅	✅
Push Message	✅	✅
Auto Metrics (DAU / Retention / Stickiness)	✅	✅
Analytics (Data Report / Chart)	✅	✅
Remote Config	✅	✅
Text Message	—	✅
Kakao Message	—	✅
In-App Message Statistics	—	✅
Push Message Statistics	—	✅
Text Message Statistics	—	✅
Kakao Message Statistics	—	✅