libtmux-mcp 0.0.1-alpha.12-SNAPSHOT · Source
Build the Java application distribution, then point the MCP client at its launcher. Run these commands from the Java repository with JDK 21 or newer and tmux installed.
Build the launcherLink to section
$ ./gradlew :libtmux-mcp:installDistThe distribution contains a bin/libtmux-mcp launcher and its required
JARs. Keep them together.
Launch it on a named socket with an inspection surface:
$ LIBTMUX_TOOLSETS=inspect \ libtmux-mcp/build/install/libtmux-mcp/bin/libtmux-mcp \ --socket-name docs-agentIt serves MCP on standard input and output. Configure the client’s command
to the launcher location. If the distribution’s bin directory is on the
client’s PATH, an mcpServers entry can use:
{ "mcpServers": { "tmux-java": { "command": "libtmux-mcp", "args": ["--socket-name", "docs-agent"], "env": { "LIBTMUX_TOOLSETS": "inspect" } } }}Verify and change selectionLink to section
Read tmux://capabilities, then call list_sessions.
Select inspect,manage,execute for workflows that create topology and
run pane commands. Reconnect after changing startup configuration.
--socket accepts a socket path; --tmux selects the tmux executable.
The environment also supports LIBTMUX_SOCKET,
LIBTMUX_SOCKET_PATH, and LIBTMUX_TMUX_CONFIG.
The retired --safety, LIBTMUX_SAFETY, --watch, and
LIBTMUX_WATCH settings fail startup. Use toolsets and bounded
observation tools instead.