Client Integrations

This page shows how to connect Local Signer MCP from common clients.

Local clients

Use stdio when the client can launch a local process on the same machine.

Typical local clients:

• Claude Desktop

• Claude Code

• Cursor

• Windsurf

• Continue

• Zed

• Cline

• other local MCP clients

Recommended local config entry:

{
  "mcpServers": {
    "local-signer": {
      "command": "NODE_BINARY_PATH",
      "args": ["SIGNER_ENTRYPOINT_PATH"],
      "env": {
        "LOCAL_SIGNER_EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY",
        "LOCAL_SIGNER_EVM_RPC_URL": "YOUR_RPC_URL"
      }
    }
  }
}

If the client can launch docker, use a container wrapper instead of a direct binary path:

{
  "mcpServers": {
    "local-signer": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "--env-file",
        "LOCAL_SIGNER_ENV_FILE",
        "allbridge/local-signer-mcp:latest",
        "node",
        "dist/index.js"
      ],
      "env": {}
    }
  }
}

This keeps the command line short and moves the signer variables into a host-side env file.

Remote connectors

Use streamable-http only when the client requires a URL.

If the client insists on https://, place TLS in front of the signer or expose the signer through a trusted proxy.

Recommended remote config entry:

{
  "mcpServers": {
    "local-signer": {
      "url": "https://your-signer.example.com/mcp"
    }
  }
}

Claude Desktop

Open Settings -> Developer -> Local MCP servers -> Edit Config. Add local-signer as another entry in mcpServers; do not overwrite existing servers.

What to remember

• add local-signer as one more entry in the registry

• do not replace the rest of the config file

• keep secret values outside the command line