worktree-orbit-mcp
# worktree-orbit-mcp
Worktree Orbit is a local MCP for developers who keep several Git worktrees alive at once. It answers whether a repository has parallel worktrees, whether they are clean, and whether detached, locked, or prunable worktrees need attention.
## Tool
- `inspect_worktree_topology`: returns aggregate worktree count, primary and linked counts, clean or dirty counts, detached state, lock state, prunable state, and a coarse topology hint.
It never returns paths, branch names, hashes, remotes, lock reasons, subjects, authors, or file contents.
## Safety
- Local Git commands only. No network access is used.
- The selected repository must stay inside `WORKTREE_ORBIT_ROOT`.
- Commands are read-only: the server does not add, remove, move, lock, unlock, reset, prune, or modify worktrees.
- Worktree status checks are bounded and time limited.
- Results are aggregate signals, not a replacement for inspecting a specific worktree before deleting it.
## Run
```bash
npm install
npm run build
node dist/index.js
```
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly described, making selection unambiguous.
The tool name 'inspect_worktree_topology' follows a clear verb_noun pattern in snake_case, which is consistent and predictable. As a single tool, it sets a clear convention.
The server has only one tool, which is on the low end of typical tool counts. While the narrow scope of inspection might justify a single tool, the server name suggests a broader worktree management capability, making the count feel slightly thin.
The tool provides a comprehensive inspection summary, but lacks any management operations (create, delete, prune, etc.) that the server name 'worktree-orbit' implies. This leaves significant gaps in the tool surface for full worktree lifecycle coverage.