Back to Browse

Termmux MCP Server

Developer ToolsModerate5.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Drive local tmux sessions, windows and panes: list, create, send keys, capture output.

About

Drive local tmux sessions, windows and panes: list, create, send keys, capture output.

Security Report

5.7
Moderate5.7Moderate Risk

termmux is a local stdio MCP wrapper around the tmux CLI that runs commands via execFile with argument arrays and no shell, and its tools match its stated purpose. The main consideration is that send_keys lets an AI assistant type arbitrary commands into the user's tmux panes, which is inherent to the feature but should be understood. A minor option-injection risk exists where user-supplied values are passed to tmux without a leading "--" separator. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

process_spawn

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-termmux": {
      "args": [
        "-y",
        "@reneturcios/termmux"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

termmux

Drive local tmux from the command line or as a stdio MCP server. List, create, rename and kill sessions; manage windows and panes; send keys to a pane and capture its visible output.

Every operation runs the real tmux binary with an argument array (execFile, never a shell string) behind an injectable executor, so session names and key text are never reinterpreted as shell syntax. Name a session that does not exist and you get tmux's own error back. When no tmux server is running, list calls return empty lists — the same empty world tmux reports.

Install

npx -y @reneturcios/termmux mcp

Requires a tmux binary on the host (the container image bundles none, so containerised runs report tmux unavailable).

CLI

termmux mcp
termmux list-sessions
termmux create-session <name> [window] [start-dir]
termmux kill-session <name>
termmux list-windows <session>
termmux capture <session> [pane]
termmux send <session> <keys...>
termmux --version

Exit codes: 0 success, 1 tmux error, 2 usage error.

MCP tools

ToolPurpose
list_sessionsList all tmux sessions
create_sessionCreate a new tmux session
kill_sessionKill a tmux session by name
list_windowsList the windows of a tmux session
create_windowCreate a new window in a tmux session
kill_windowKill a window in a tmux session
list_panesList the panes of a tmux session, optionally of one window
send_keysSend keys (a command line or key names) to a tmux pane
capture_paneCapture the visible contents of a tmux pane as text
rename_sessionRename a tmux session
select_windowSelect (activate) a window in a tmux session
get_session_infoGet details of one tmux session

MCP client config:

{
  "mcpServers": {
    "termmux": {
      "command": "npx",
      "args": ["-y", "@reneturcios/termmux", "mcp"]
    }
  }
}

Docker

docker run -i ghcr.io/cloudcorprecords/termmux          # MCP server (tmux unavailable in-image)
docker run --rm ghcr.io/cloudcorprecords/termmux --version

Development

npm install
npm run build
npm test

MIT license.

Reviews

No reviews yet

Be the first to review this server!