Pane (runpane MCP server)
Pane
runpane MCP server: an agent in any repository opens Pane panels, starts other agents and reads their status
- 586 ★ on the repository
- Last commit
Broad access
Why this level
- Starts coding agents in panels, sends them text and keystrokes and reads their terminal screens
- Wider toolsets add commit, push, rebase, stash and other writing git operations
- At launch the app writes its own pane server into the Claude Code, Codex and Cursor configs
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/paneDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Starts coding agents in panels, sends them text and keystrokes and reads their terminal screens
- Wider toolsets add commit, push, rebase, stash and other writing git operations
- At launch the app writes its own pane server into the Claude Code, Codex and Cursor configs
This is third-party code. Review the repository files before installing.
What it does
Pane is an open-source app where several coding agents run in parallel, each in its own git worktree. The `runpane mcp` command starts an MCP server through which an agent calls Pane commands as tools. An agent in any repository can set up a repository and a panel for a task, open a tab with another agent and read that agent's terminal screen. The core toolset is on by default, and each of the three main jobs takes one call. The agents_start tool starts an agent on a task, waits until it is ready and returns ids and a pane:// link. The agents_status tool reports whether the agent is working, waiting for a person, idle or exited. The agents_send tool passes a follow-up and says whether the agent took it or queued it. Other toolsets are switched on with the `--toolsets` flag, for example git, sessions and admin. The git set covers commit, push and pull, plus rebase. The `--read-only` flag keeps only read tools. Pane documentation search and reading work offline.
Who it is for. For developers who run Claude Code, Codex and Cursor on several branches at once.
Good fit when
- A lead agent works through a task list and must create a separate worktree panel for each task and start Codex in it
- A finished branch needs a tab with another agent for a review or audit in the same panel
- You want to ask an agent whether any running agent is waiting for your decision, without opening the Pane window
- You need a pane:// link that opens a specific panel or repository in the app
- An agent has to search Pane's docs and runpane help without network access
Not a fit when
- You work with one agent on one branch: orchestration through Pane adds nothing
- You need strictly limited access: the all set includes tools that write to git
- You need a standalone server without panels and worktrees: the tools manage a Pane workspace
- An agent gets lost in a large tool catalog: keep the core set, which is deliberately short
Example request
Create a separate Pane panel for the API timeout task, start Codex in it and tell me in a couple of minutes whether it has finishedMCP
- Transport
- stdio
- Authentication
- not required
Limitations
- Agents start only in Pane panels, and the server manages that workspace.
- The core set exposes 16 tools because a long list makes smaller models choose worse. The other sets can also be switched on in the app settings under AI & Agents.
- The app registers the server only in packaged builds and only for detected Claude Code, Codex and Cursor clients. A pane entry you added by hand through npx stays untouched on updates and when the setting is turned off.
- The license is AGPL-3.0. Next to the app the repository holds a separate runpane package for installation and remote host setup.
How to disable. In the app open Settings, the AI & Agents section, and switch off registering Pane tools with Claude Code, Codex and Cursor: the app removes its own entry from each config. A server added by hand is removed with claude mcp remove pane or by editing the client config.
FAQ
How do I connect Pane to Claude Code as an MCP server?
Run `claude mcp add --scope user pane -- npx --yes runpane@latest mcp`. The --scope user option makes the server available in all your projects. `claude mcp list` checks the connection.
Which Pane MCP tools are on by default?
The core set. Its tools start an agent, check its status and send follow-ups, create tabs and send keys. They also show repositories, panels and workspace state, and archive and restore panels. Building pane:// links, docs search and the doctor diagnostic are part of it too.
How do I limit Pane MCP to read-only?
Start the server with the --read-only flag: it keeps only the read tools from the selected sets. Sets are chosen as a list, for example runpane mcp --toolsets core,git. The read set bundles every read-only tool.
How is starting an agent in a new panel different from an existing one?
For new work pass repo and name to agents_start, and Pane creates a panel with a worktree and a branch. For reviews, audits, fixes and QA pass pane, and the agent opens as a new tab in the existing panel.
How do I connect Pane MCP to Cursor or VS Code?
In Cursor add the pane entry from the install methods section to `~/.cursor/mcp.json`. For VS Code use `.vscode/mcp.json` or the MCP: Add Server command. Cursor may ask to approve the server, and the Cursor CLI sometimes needs `agent mcp enable pane`.
Discussion
No questions or reviews yet.
Related
MCP serversA Dagger MCP server that gives each agent its own container and git branch for safe parallel work
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A local encrypted Slack and Discord alternative where AI agents work in channels alongside people through REST or MCP over a P2P mesh
An MCP server that lets Claude Code, Codex and other agents call Gemini, GPT, Grok and local models for review, debugging and consensus
An MCP bridge: a single run_python tool runs code in a container and calls your MCP servers
A zero-dependency Python CLI: one catalog of MCP servers and skills for every agent, with only a compact index in context
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Pane (runpane MCP server) (this entry) | yes | not required | 586 | |
| Claude Squad | no | 8,694 | a terminal app for running several agents in parallel | |
| Orca | no | 110,221 | a desktop environment for parallel agents in separate git worktrees |
README in short
The docs/PANE_MCP.md file covers server registration, a table of toolsets and manual setup for other clients. The main README covers the app itself, Remote Pane access and handing tasks between machines over Tailscale.