Tmux MCP 926c4b5b

MCP开发工具

提供方 heaus

开发工具 stdio · 本地进程 会话登录 社区 / 第三方 Cursor
查看接入方式

为Cursor的Model Context Protocol构建的tmux代理,用于在远程tmux会话中执行命令、捕获输出并保持完整的历史记录。

一句话选型结论

按资料字段整理

Tmux MCP 926c4b5b 属于开发工具类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Cursor,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 8 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量8暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

远程控制Python本地部署命令行工具SSH管理自动化脚本审计日志

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
python -m venv .venv

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 8 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 8 个工具,职责相对集中,接入后不容易误操作。
  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Tmux MCP 926c4b5b当前 8 stdio · 本地进程 本地部署 有 2026-05-17
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方heaus上游标注的维护方 heaus
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.4 KB
来自项目仓库与上游目录的原文,未做删改

Cursor MCP tmux Agent (Broadcom Internal)

The tmux MCP agent is built specifically for Cursor's Model Context Protocol and is intended for internal BRCM workflows. It gives Cursor a persistent foothold inside a remote tmux session so the assistant can issue commands, capture output, and keep a fully auditable history of everything it does.

The agent opens a single Paramiko SSH connection per profile and reuses it for every tmux interaction. This keeps command latency low and avoids repeatedly spawning local ssh processes.

Requirements

  • Operating system: macOS or Windows with WSL (the agent cannot run inside our VDI environment because it needs a locally installed Python toolchain and packages).
  • Python 3.11 or later on the machine running Cursor.
  • A reachable remote host with:
  • ssh access.
  • tmux installed and discoverable in PATH.
  • (Optional) Host aliases defined in ~/.ssh/config so the agent can hydrate profiles automatically.

Installation

Python version and environment

The python -m venv .venv command asks Python to create a virtual environment in the .venv/ directory so the agent's dependencies do not leak into your global interpreter. The agent is tested against Python 3.11.11.

If you need Python 3.11.11 specifically:

  • macOS – Install it system-wide with Homebrew (brew install python@3.11).
  • WSL / Linux – Install from your package manager (e.g. sudo add-apt-repository ppa:deadsnakes/ppa && sudo apt install python3.11 python3.11-venv).

Package setup

  1. Copy this package into your target directory.
  2. Create an isolated Python environment inside that directory and install the runtime dependencies (replace `` with the absolute path where you extracted the source code):bash cd <your_directory>/tmux_mcp python -m venv .venv source .venv/bin/activate pip install -r requirements.txt

Cursor MCP Setup

The package includes .cursor/mcp.json, which registers the agent with Cursor as an stdio MCP server. Open the workspace in Cursor and it will launch the agent automatically. If you need to change the command, environment variables, or working directory, edit that file before opening the project.

If you are integrating with another MCP client, you can use the following template. Replace `` with the same absolute path used above so the MCP host executes the virtualenv interpreter and startup script directly:```json
{
"mcpServers": {
"tmux-mcp-agent": {
"type": "stdio",
"command": "<your_directory>/tmux_mcp/.venv/bin/python",
"args": [
"<your_directory>/tmux_mcp/scripts/start_mcp_agent.py",
"--log-level", "INFO",
"--session", "cursor-shared",
"--window", "agent",
"--pane", "0"
]
}
}
}


Place the JSON wherever your MCP host expects server definitions and ensure the `tmux_mcp` package is importable.

The top-level fields mean:

- `type` – Must remain `stdio`; Cursor communicates with the agent over stdin/stdout.
- `command` – Absolute path to the Python interpreter that should launch the agent (typically the `.venv/bin/python` inside this project).
- `args` – Ordered list of arguments given to that interpreter. The first element should be the launcher script followed by any CLI flags you want to pass through.

### MCP server arguments

The startup script `scripts/start_mcp_agent.py` forwards CLI options to `tmux_mcp.agent`. You can adjust any of these in the `args` array:

- `--log-level` – Logging verbosity (`DEBUG`, `INFO`, `WARNING`, `ERROR`).
- `--session` – Default tmux session to create/attach (default: `cursor-shared`).
- `--window` – Default tmux window name (default: `agent`).
- `--pane` – Default tmux pane identifier (default: `0`).
- `--log` – Path to the structured log file (default: `logs/agent_activity.log`).

Add or remove options as needed; Cursor will pass them verbatim when launching the MCP server.

## Working With tmux Sessions

1. Use the `list_profiles` and `upsert_profile` tools to manage encrypted SSH connection profiles. Supplying only a `name` and `source_host` is enough when the host exists in `~/.ssh/config`; the agent will inherit hostname, user, port, identity files, and common options automatically.
2. Cursor typically calls `health_check` followed by `connect_session`. Provide the profile name plus the desired tmux `session`, `window`, and optional `pane` identifiers.
3. To run commands, invoke `submit_command`. If safe mode flags a command, respond with `approve_command` or `reject_command` using the returned `command_id`.
4. Retrieve live context from a pane at any time with `read_context`.

**Example (Cursor chat prompt)**```
Connect to the tmux server using profile &quot;staging&quot;, session &quot;cursor&quot;, window &quot;agent&quot;.

Cursor will translate that message into a connect_session tool call:```json
{
"profile": "staging",
"session": "cursor",
"window": "agent"
}


Once connected, you can follow up with prompts such as “Run `npm test` in the current pane,” and the agent will send the command via `submit_command`.

**Example (create or update a profile)**```
Create an SSH profile called &quot;staging&quot; for host 203.0.113.15 using user &quot;deploy&quot; and key file &quot;/Users/bo/keys/staging.pem&quot;.

Cursor translates that into an upsert_profile tool call similar to:json { &quot;profile&quot;: { &quot;name&quot;: &quot;staging&quot;, &quot;hostname&quot;: &quot;203.0.113.15&quot;, &quot;username&quot;: &quot;deploy&quot;, &quot;identity_file&quot;: &quot;/Users/bo/keys/staging.pem&quot; } }

Subsequent “Connect to staging” prompts reuse the stored profile automatically. Call upsert_profile again with the same name to overwrite credentials or ports when they change.

The agent ensures the target session and window exist, creates them when necessary, and keeps a persistent pane snapshot so it can report only the delta after each command.

Logging & Auditing

Every command, approval decision, and captured output delta is appended to logs/agent_activity.log as JSON Lines. Each record includes the Cursor task identifier plus the tmux session/window/pane, making it easy to trace parallel tasks that share the same tmux session.

Troubleshooting

  • Paramiko TripleDES warning – The current Paramiko release still references TripleDES. The cryptography library marks it as deprecated, so you may see CryptographyDeprecationWarning in the logs. It is a harmless warning; newer Paramiko releases will remove the legacy cipher automatically.
  • SSH connection issues – Confirm the profile’s identity file exists locally and that any ProxyCommand or IdentitiesOnly options are valid. The agent reports these errors back through SessionError messages.
  • tmux not found – Make sure tmux is installed on the remote host and available in the PATH exposed to the SSH session.

Customisation

  • Default feature flags live in src/tmux_mcp/config/feature-flags.yaml. Adjust them to change safe-mode behaviour or approval patterns.
  • Capability definitions are in src/tmux_mcp/config/capabilities.json. Update this file if you add or rename tools/resources.
  • When you add new connection profiles by hand, remember that the agent stores them encrypted on disk using Fernet; deleting .tmux_mcp/ will remove locally cached profiles.

Support

If Cursor reports that the MCP server is unavailable, run python -m tmux_mcp.agent --log-level DEBUG from a terminal to inspect the startup logs. Open an issue with the collected logs if you need further assistance.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Tmux MCP 926c4b5b 怎么安装?

在客户端按下面的安装命令接入:python -m venv .venv。装完在客户端配置里引用同一个包或端点。

Tmux MCP 926c4b5b 怎么在 Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Tmux MCP 926c4b5b 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Tmux MCP 926c4b5b 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Tmux MCP 926c4b5b 支持哪些客户端?

资料标注支持 Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Tmux MCP 926c4b5b 能提供哪些能力?

资料显示约 8 个工具;能力标签包括 远程控制、命令行工具、Python、Cursor、审计日志。具体工具清单以官方文档为准。

Tmux MCP 926c4b5b 需要什么运行环境?

运行时为 Python;属于本地进程,需要在本机装好运行环境。

Tmux MCP 926c4b5b 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。