tmux-mcp

NPM · @FR1SK/TMUX-MCP · SCANNED AUG 7

MCP server for tmux — browse sessions, capture output, send commands.

Available components

+23 this week 66 66 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency19

Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 93 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 1368 tokens (~97/item across 14 items; 14 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management40

Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @fr1sk/tmux-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add fr1sk-tmux-mcp -- npx -y @fr1sk/tmux-mcp

# add to Codex CLI

codex mcp add fr1sk-tmux-mcp -- npx -y @fr1sk/tmux-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fr1sk-tmux-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@fr1sk/tmux-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add fr1sk-tmux-mcp --command npx --arg -y --arg @fr1sk/tmux-mcp

# ~/.hermes/config.yaml

mcp_servers:
  fr1sk-tmux-mcp:
    command: "npx"
    args: ["-y", "@fr1sk/tmux-mcp"]

// mcp.json

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

6 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
4 Aug 26 +5
- Stability: unverified → 0.30 ▲ functional
2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
1 Aug 26 −28
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 +3
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Install scripts: unverified → pass ▲ security
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
29 Jul 26 +20
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
28 Jul 26 −20
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
27 Jul 26 40

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Aug 2026 · Analysed npm/@fr1sk/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	npm

Dependencies 95 packages

Packages resolved	95
Deprecated	95
Stale	29
Tree resolution	Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools · 14 exposed · ~1,368 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

capture_pane ~179

Capture current output of a tmux pane. Target format: 'session:window.pane' (e.g. 'work:0.0'). Use list_sessions → list_windows → list_panes to build the target. WARNING: pane output may contain environment variables, API keys, tokens, and credentials — do not call if the pane may contain sensitive data unless the user has confirmed it is safe. AFTER displaying the output, always ask the user what to do next with these options: Refresh (call capture_pane again), Send command (ask what command then call send_keys), Switch pane (restart from list_sessions), Done (stop). Loop until the user picks Done.

Input Output Examples

Name	Type	Req	Description
lines	integer	–	Lines of scrollback to include (default: 150)
target	string	yes	Pane target: 'session:window.pane'

No output schema declared.

No examples provided.

get_config ~89

Returns the current tmux-mcp configuration: whether tmux is installed, the default session name, and whether the agent is configured to always route shell commands through tmux. Call this at the start of any task to check how the agent should behave. If alwaysUseTmux is true, route all shell commands through send_keys in the configured session instead of direct Bash for the remainder of the task.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

kill_pane ~62

Kill a tmux pane and terminate its running process. ALWAYS confirm with the user before calling — this is destructive and cannot be undone. Target format: 'session:window.pane'.

Input Output Examples

Name	Type	Req	Description
target	string	yes	Pane target: 'session:window.pane'

No output schema declared.

No examples provided.

kill_session ~47

Kill a tmux session and all its windows and panes. ALWAYS confirm with the user before calling — this is destructive and cannot be undone.

Input Output Examples

Name	Type	Req	Description
session	string	yes	Session name to kill.

No output schema declared.

No examples provided.

kill_window ~56

Kill a tmux window and all its panes. ALWAYS confirm with the user before calling — this is destructive and cannot be undone. Target format: 'session:window'.

Input Output Examples

Name	Type	Req	Description
target	string	yes	Window target: 'session:window'

No output schema declared.

No examples provided.

list_panes ~107

List panes in a tmux target. Pass a session name ('work') or session:window ('work:0'). When only a session name is passed, lists all panes across all windows in that session. Returns pane index, size, active status, and running command. If there is only one pane, auto-select it without asking. If multiple, present them as choices and ask the user which pane to use.

Input Output Examples

Name	Type	Req	Description
target	string	yes	Session name or 'session:window'

No output schema declared.

No examples provided.

list_sessions ~124

List all active tmux sessions. Returns session name, window count, creation time, and attached status. WHEN TO CALL: Call this immediately whenever the user mentions tmux, asks to attach a session, wants to see terminal output, check logs, run a command in a pane, or interact with any running process. Do not answer from memory — always call this tool first to get live state. WORKFLOW: After getting sessions, ask the user which session, call list_windows, ask which window, call list_panes, ask which pane, then call capture_pane.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_windows ~67

List all windows in a tmux session. Returns window index, name, pane count, and active status. If there is only one window, auto-select it without asking. If multiple, ask the user which window to use.

Input Output Examples

Name	Type	Req	Description
session	string	yes	Session name (from list_sessions)

No output schema declared.

No examples provided.

new_session ~89

Create a new detached tmux session. Before calling, use list_sessions to check whether a session with the requested name already exists.

Input Output Examples

Name	Type	Req	Description
command	string	–	Shell command to run immediately in the first window. WARNING: executes in your shell.
cwd	string	–	Working directory for the session.
name	string	–	Session name. Omit to let tmux auto-assign one.

No output schema declared.

No examples provided.

new_window ~74

Create a new window in an existing tmux session.

Input Output Examples

Name	Type	Req	Description
command	string	–	Shell command to run immediately. WARNING: executes in your shell.
cwd	string	–	Working directory for the new window.
name	string	–	Window name.
session	string	yes	Session name to create the window in.

No output schema declared.

No examples provided.

rename_session ~36

Rename an existing tmux session.

Input Output Examples

Name	Type	Req	Description
new_name	string	yes	New session name.
session	string	yes	Current session name.

No output schema declared.

No examples provided.

rename_window ~50

Rename a window in a tmux session. Target format: 'session:window'.

Input Output Examples

Name	Type	Req	Description
new_name	string	yes	New window name.
target	string	yes	Window target: 'session:window'

No output schema declared.

No examples provided.

send_keys ~232

Send keys or a command to a tmux pane, then capture its output. Target format: 'session:window.pane'. Use enter=false for raw tmux key sequences like 'C-c', 'Escape', or arrow keys — these are not shell commands and must not have Enter appended. Use enter=true (default) for shell commands. Set wait_ms higher for long-running commands; 0 captures immediately before output appears. WARNING: this executes arbitrary commands in your shell — only use with trusted input.

Input Output Examples

Name	Type	Req	Description
capture_lines	integer	–	Lines to capture after sending (default: 50)
enter	boolean	–	Press Enter after keys (default: true). Set false for raw key sequences like C-c, Escape, arrow keys.
keys	string	yes	Command or key sequence (tmux notation: 'C-c', 'Escape', 'Up', etc.)
target	string	yes	Pane target: 'session:window.pane'
wait_ms	integer	–	Milliseconds to wait before capturing (default: 400). Set higher for slow commands, 0 to capture immediately.

No output schema declared.

No examples provided.

split_pane ~156

Split a tmux pane horizontally or vertically. 'horizontal' = left/right panes side by side. 'vertical' = top/bottom panes stacked. Target format: 'session:window.pane' or 'session:window'.

Input Output Examples

Name	Type	Req	Description
command	string	–	Shell command to run in the new pane. WARNING: executes in your shell.
cwd	string	–	Working directory for the new pane.
direction	string	–	'horizontal' splits left/right, 'vertical' splits top/bottom (default: horizontal)
size	integer	–	Size of the new pane as a percentage (e.g. 50).
target	string	yes	Target pane or window to split: 'session:window.pane'

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 7 Aug

Day	Score
27 Jul	40
28 Jul	20
29 Jul	40
31 Jul	43
1 Aug	15
2 Aug	60
3 Aug	60
4 Aug	65
5 Aug	65
6 Aug	66
7 Aug	66