Migrating from a Local Server

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

Why should you migrate?

• No installation / updates needed. You're free from npm package management, 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 are applied immediately without a client update.

Key changes

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

Item	Local Server	Remote Server
Add method	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. Remove the existing local server settings (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.

If you have only used the claude.ai web, this step does not apply.

After — local server:

{
  "mcpServers": {
    
  }
}

2. Add the remote server as a connector

• claude.ai web: Left sidebar Settings → 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. Direct link

• Claude Desktop: Same flow.

You can use the same API key value you were using before.

3. Verify the integration

In a new conversation:

Tell me the available Hackle tools

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

Clean up the local server package (optional)

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

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

If you were running it with npx -y, just clearing the cache is enough.

npx clear-npx-cache

Tool compatibility

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

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	—	✅

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

FAQ

How long will the local server keep working? Since new features and tools are added only to the remote server, we recommend migrating as soon as possible. The local MCP server will no longer be updated, and support is scheduled to end within the second half of 2026.

If I move to the remote server, is my data sent externally? The remote server is operated on Hackle's infrastructure. The AI client's requests query and respond with workspace data through the Hackle MCP server, without going through any separate external system.

Can I keep using my existing API key? Yes, you can use your existing key as is.