MCP Setup

The MCP server supports local stdio transport and streamable HTTP transport.

Prerequisite

Start mutx-tui first. The MCP server expects the TUI socket at:

/tmp/mutx/mutx.sock

You can override the socket path for the TUI with MUTX_SOCKET_PATH or mutx-tui --socket-path ....

stdio mode

mutx-mcp

This is the default mode and the best choice when the agent runs on the same machine.

Example client configuration:

{
  "mcpServers": {
    "mutx": {
      "command": "mutx-mcp"
    }
  }
}

HTTP mode

mutx-mcp --mode http --bind 0.0.0.0:8000

HTTP mode exposes:

• MCP endpoint: http://HOST:8000/mcp
• health check: http://HOST:8000/health

Use this mode when:

• the agent cannot spawn local processes
• you want to front MUTX with a container
• you need a shared MCP endpoint on a trusted local network

Container example

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

If the TUI is also containerized, mount the same /tmp/mutx directory into both containers.

Operational notes

• mutx-mcp is stateless
• if the TUI is not reachable, tool calls fail immediately
• wallet approvals still happen in the TUI, even when MCP is served over HTTP