Connect a Go MCP client

github.com/libtmux/libtmux-go/mcp · Source

Install the Go MCP command and verify its effective configuration before connecting a client. Go 1.26 or newer is required to build it.

Install the commandLink to section

$ go install github.com/libtmux/libtmux-go/mcp/cmd/libtmux-mcp@latest

Make Go’s binary installation directory available to the MCP client’s PATH. The server also needs tmux 3.2a or newer.

Inspect the selectionLink to section

This reports the effective tool list without resolving or contacting tmux:

$ LIBTMUX_TOOLSETS=inspect libtmux-mcp -tools

Diagnose the endpoint separately:

$ libtmux-mcp \
    -doctor \
    -socket-name docs-agent

The report includes the tmux version, endpoint, topology, and caller context. A daemon that has not started yet is not a configuration error.

Connect a clientLink to section

For a client using mcpServers:

{
  "mcpServers": {
    "tmux-go": {
      "command": "libtmux-mcp",
      "args": ["-socket-name", "docs-agent"],
      "env": {
        "LIBTMUX_TOOLSETS": "inspect"
      }
    }
  }
}

Add the execute toolset when the client needs to create tmux objects or run commands. Reconnect after changing startup configuration.

Choose a socket path or name; conflicting selectors fail startup. -binary selects the tmux executable. A client’s curated environment may have a different PATH or locale from your shell; compare the doctor report with the tmux binary that started your sessions.

Launcher reference.