Deployment

This page covers the public deployment shapes for MUTX.

Local binaries

This is the simplest setup:

1. Run mutx
2. Run mutx-link
3. Configure the agent to spawn mutx-link

Use this when the operator, the TUI, and the agent all live on the same host.

Split local TUI plus containerized Link

This is useful when the agent expects an HTTP endpoint or when you want to keep the Link runtime isolated.

Requirements:

• MUTX running on the host
• shared socket directory mounted into the Link container

Example:

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

Fully containerized

You can containerize both components, but MUTX still needs:

• -it for interactive terminal access
• persistent config and data volumes
• a shared /tmp/mutx mount so the Link container can reach the socket

Health checks

In HTTP mode, Link exposes:

• /health for liveness
• /mcp for the actual MCP transport

Logging

mutx can write structured logs to file and export them with:

mutx logs export

Useful flags:

• --category
• --level
• --since
• --until
• --encrypt