Worktree Manager MCP
An MCP server for a desktop git worktree manager, so an agent creates branches in separate folders and checks status.
- 64 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Advanced tools commit and push to the user's repositories.
- The app can expose the workspace and its terminal to a browser, including through an ngrok tunnel.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/worktree-managerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Advanced tools commit and push to the user's repositories.
- The app can expose the workspace and its terminal to a browser, including through an ngrok tunnel.
This is third-party code. Review the repository files before installing.
What it does
Worktree Manager is a Tauri desktop app plus the `@worktree-manager/mcp` package. The app keeps workspaces made of several repositories: a new worktree appears in every linked project at once, while `node_modules`, `target` and similar folders are symlinked. The MCP server gives an agent three tool layers. The core layer lists workspaces and worktrees and reports status. The detail layer returns branches, diff statistics and changed files. The advanced layer creates and archives worktrees, commits and pushes. While the app runs, the server talks to it over local HTTP. Without the app it reads the configuration file.
Who it is for. Developers who keep several branches going in parallel, run Claude Code, Codex or Cursor in different worktrees and want to manage them from the agent's chat.
Good fit when
- An urgent hotfix interrupts feature work and you need a separate folder with a branch instead of `git stash`.
- Frontend, backend and a shared library live in different repositories and the branch must appear in all of them.
- The agent should report which worktrees hold unpushed changes.
- Several agents work on different branches of one project and must not interfere with each other.
- After a merge, old worktrees should go to the archive with a check for uncommitted work.
Not a fit when
- Work happens in a single branch of one repository and worktrees add nothing.
- The desktop app cannot be installed: without it the MCP server only reads the configuration file.
- The agent must not commit or push and you have not set up confirmation for each call.
Example request
Create a feature-abc worktree in all projects of the workspace and show its status.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
Full operation needs the Worktree Manager app installed: builds exist for macOS, Windows and Linux. The MCP package requires Node.js 18 or newer. The app registers its port in `~/.config/worktree-manager/mcp.json`, 42819 by default, and picks a free one from 42800–42900 if that is taken. The advanced-layer tools write to git, push included, so working repository access is needed. Built-in voice input and commit-message generation use external services with separate keys.
How to disable. Run `npx -y @worktree-manager/mcp uninstall` or delete the `worktree-manager` entry from `~/.claude.json`. Remove the app the usual way for your system.
FAQ
How do I connect Worktree Manager to Claude Code?
Run `npx -y @worktree-manager/mcp install`: it installs the package and registers the server in Claude Code configuration. Then restart Claude Code or run `claude mcp restart`.
Does the app need to stay running?
For live data, yes: the server reaches the app over local HTTP. Without it the server falls back to reading `~/.config/worktree-manager/global.json`, and a "No transport available" error means neither the app nor the file is present.
What can the agent do through it?
The core layer only reads: workspaces, worktrees, status. The detail layer adds branches, diffs and changed files. Creating and archiving worktrees, `git_commit` and `git_push` sit in the third layer.
What is a git worktree and why is it better than a clone?
A worktree checks out another branch into a separate folder while history, refs and hooks stay shared. A separate clone would take space for the whole repository.
How do several repositories work together?
Group the projects into a workspace in the app. Creating a worktree then makes a branch of the same name in every linked repository, and the agent sees them together.
Discussion
No questions or reviews yet.
Related
MCP serversA git MCP server with 28 tools: an agent clones, commits, branches, merges, rebases and manages worktrees in local repositories.
A git worktree CLI with a fuzzy finder: one folder per branch so several agents can work in parallel without conflicts
A Rust git worktree manager with a TUI: it creates the branch, copies files, runs setup and shows where an AI agent works
An MCP server that gives an agent screenshots, DOM, logs and IPC of a running Tauri v2 app and lets it click through the interface
A local MCP server with call graphs and symbol search: the agent sees code structure and what an edit affects in advance.
MCP server with a work item graph and server-side gates: an agent cannot start work until the required notes exist
README in short
The project presents itself as the missing GUI for git worktrees. Besides the manager there is a built-in terminal, one-click opening in VS Code, Cursor and IntelliJ IDEA, and password-protected browser access.