Agent Integration

How to connect MUTX to specific MCP clients.

Claude Code

Add to ~/.claude.json or your project .mcp.json:

{
  "mcpServers": {
    "mutx": {
      "command": "mutx",
      "args": ["link"]
    }
  }
}

The daemon must be running before the Claude Code session starts. Start it with mutx daemon. The agent spawns mutx link as a subprocess in stdio mode. Approvals appear in the MUTX Requests tab.

Claude Desktop

Config file location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "mutx": {
      "command": "/usr/local/bin/mutx",
      "args": ["link"]
    }
  }
}

Claude Desktop may not inherit your shell PATH. Use the full path to mutx.

Custom agents (SDK)

stdio transport

Spawn mutx link as a subprocess and wire stdin/stdout. This works with any MCP SDK that supports stdio transport.

HTTP transport

Run Link in HTTP mode:

mutx link serve --mode http --bind 0.0.0.0:8000

Point your SDK’s HTTP transport at http://HOST:8000/mcp.

Docker-based agents

When the agent cannot spawn local processes, run Link in a container:

docker run --rm -p 8000:8000 \
  -v /tmp/mutx:/tmp/mutx \
  ghcr.io/mutx-net/mutx-link:latest

The agent connects to http://localhost:8000/mcp. MUTX can run natively or in its own container – both just need to share /tmp/mutx.

CLI mode

For shell scripts and Skills-based agents that prefer commands over MCP:

mutx link wallet list
mutx link wallet balance <wallet>
mutx link wallet send <wallet> <to> <amount>
mutx link slk request --name "trading" --wallets "Main" --can-send --duration 3600
mutx link address-book list
mutx link wc sessions

Full command groups:

mutx link wallet {list,receive,send,details,balance,transactions,token-list,token-send,swap}
mutx link slk {request,info,revoke}
mutx link address-book {list,add}
mutx link wc {connect,sessions,disconnect}

Use --json for machine-readable output. Use --link-socket-path to override the default socket location.