Skip to main content
Glama
Sign In
tmux-mcp

tmux-mcp

by vn-lazyming
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Open terminal

tmux_new

Create a new tmux session, window, or pane without changing the human's current view. Returns a stable pane id for later sending keys and reading output.

Instructions

Open a new tmux session, window or pane without switching the human's view.

Returns its pane id (e.g. "%7") for tmux_send/tmux_read: unlike "ming:0.1" it stays on this pane when the human renames the session or splits the window.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "tmux_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoStarting directory, relative to home; empty = home.
kindNo"session" = its own `tmux attach -t NAME`; "window" = a new window in `session`; "pane" = a split of `session`'s current windowsession
nameYesName with no spaces, ":" or ".", e.g. "ming". A session is then reachable with `tmux attach -t ming`.
sessionNoFor window/pane: the session to add it to; empty = the agent session "agent"

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare non-read-only, non-idempotent, non-destructive, so the description does not need to restate safety. It adds real behavioral value instead: creation does not disturb the human's current view, and the returned pane id ("%7") survives session renames and window splits — a stability property an agent could not infer from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the primary effect front-loaded, and the second sentence devoted entirely to the non-obvious return-value detail. Nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still clarifies the identifier format agents will pass onward, which is the highest-risk ambiguity here. It stops short of covering failure modes — name collisions, missing session for window/pane, whether the pane is attached — leaving a small gap for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including enum semantics for `kind` and the naming pattern for `name`, so the baseline is 3. The description adds only the pane-id format example, not any parameter-level meaning beyond what the schema already carries.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Open a new tmux session, window or pane") plus a distinguishing scope note ("without switching the human's view") that separates it from nav-style siblings like tmux_move. An agent can tell exactly what gets created and what the return value is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies downstream usage by naming tmux_send/tmux_read as consumers of the returned pane id, which is useful routing. But it never states when to choose among session/window/pane at the tool level, nor when to prefer tmux_move or tmux_kill instead; the session/window/pane guidance lives in the schema, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools