$ loading_
Let AI control terminal panes, workspaces, input, and browser actions.
The materials indicate this is mainly a local wrapper around the cmux CLI for controlling terminal panes, workspaces, input, and a browser, with no declared secrets or fixed remote endpoints. Overall it looks like a local automation tool; the main concerns are local code execution and indirect access to local sessions/data, while open-source visibility helps but weak adoption and unknown maintenance warrant caution.
The material explicitly states there are no required secrets or environment variables, and no API tokens, account passwords, or other sensitive credentials are mentioned; based on the available facts, there is no clear credential collection or misuse surface.
No remote host is declared, and the description does not indicate that user data is sent to external services; based on the stated facts, it appears to be a local CLI/session control wrapper rather than a networked service.
The system flags it as executes-code, and the description says it wraps the cmux CLI to control terminal panes, workspaces, input, and a browser. This implies local command/session control and related local capabilities, which is a typical MCP-level local execution surface and should be used with least privilege.
The description indicates control over terminal sessions and workspace input, which typically implies indirect access to local session contents, command output, and related working-directory data visible to the current user. No extra sandboxing or permission boundary is described, so it should be treated as having some local data exposure surface, though there is no evidence of overbroad permissions beyond its stated function.
It is open source and MIT-licensed, which materially improves auditability and lowers risk; however, the source is a third-party registry listing, community adoption is 0 stars, maintenance status is unknown, and the README is absent, so maturity and ongoing maintenance signals are weak and supply-chain trust should still be treated with caution.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "cmux-mcp" yet — see the docs or source repo.
Use cmux-mcp to create a workspace with 3 terminal panes: run the frontend dev server on the left, the backend service on the top-right, and live logs on the bottom-right, then send the relevant commands.
A multi-pane workspace is created, with each pane running the assigned task or log view.
Using cmux-mcp, open an operations workspace, run disk, memory, and container status checks in separate panes, and summarize any anomalies.
Multiple inspection commands are executed and a clear anomaly summary is returned.
Use cmux-mcp to start a local app in the terminal, open the local URL in a browser, inspect page errors, and correlate them with terminal logs.
The app is launched and the page opened, with a correlated analysis of browser issues and terminal logs.
Let AI control local or remote terminals and interactive TUI apps.
Programmatically manage tmux sessions, windows, and panes for terminal automation.
Run commands and control a persistent tmux terminal session remotely.
Control a persistent terminal via MCP for commands, SSH, and containers.
Manage concurrent terminals for async commands, batch operations, and live monitoring.
Let AI control a browser for web tasks, extraction, and testing.