batuta-mcp
This server facilitates parallel, conflict-free development by breaking a large task into isolated plans and preparing a separate Git environment for each.
Decompose a brain dump into parallel plans: Provide a free-form description of work, and the server splits it into 2–5 plans, each with a title, spec, branch slug, and disjoint
fileBoundaries. It auto-corrects overlapping boundaries once if needed, returning metadata likeoverlapsResolvedandattempts.Check for file boundary overlaps: Given a list of plans, validate that no two plans share the same files. Returns an
okboolean and details of any detected overlaps.Scaffold isolated git worktrees: For a given repository path and set of plans, create a separate
git worktreefor each plan. Includes pre-flight safety checks (valid git repo, no overlapping boundaries, no path traversal). Each result includes the worktree path, the git command used, and a ready-to-paste agent prompt. Supports adryRunmode to preview actions without modifying the disk.
Creates git worktrees for each plan, enabling isolated development environments with a suggested prompt for each worktree.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
batuta-mcp
Split a task into plans with disjoint file boundaries, then scaffold a git worktree per plan — so parallel agents never step on each other.
A stateless MCP server that turns a brain dump into conflict-free parallel work.
Retired
Claude Code now does this itself. Splitting work across isolated worktrees so parallel agents do not collide is built in, which is what this existed to provide.
The repository is archived and read-only. It still works — nothing was removed from npm, and the last published version keeps installing — but it will not be maintained, and it does not need to be. If you want the idea rather than the package, the whole design is in
docs/and the licence lets you take it.
Related MCP server: mmm-team-orchestrator
Why
Running several coding agents in parallel is fast — until two of them edit the same file and silently clobber each other's work. The fix isn't live coordination; it's separation: give each agent a set of files that don't overlap, and the conflict can't happen by design.
batuta-mcp is the brain that does that split. You hand it a brain dump; it returns plans with disjoint file boundaries, and scaffolds an isolated git worktree for each one.
How it works
It's a stateless MCP server (stdio). No database, no daemon, no web UI — just three tools that compose:
Decompose a brain dump into 2–5 plans whose
fileBoundariesdon't overlap (auto-corrects once if they do).Check that the boundaries are truly disjoint.
Scaffold a
git worktreeper plan, returning a ready-to-paste prompt for each — open them in separate terminals/tabs and let one agent work each, conflict-free.
The "muscle" (running the agents, the terminals) stays in your editor; batuta-mcp is just the planning brain.
Features
🧠 Disjoint decomposition — plans are generated so no file appears in two plans.
♻️ Auto-correction — if the model returns overlapping boundaries, it retries once to separate them.
🌳 Worktree scaffolding — one isolated
git worktreeper plan, with a ready-to-paste prompt.🔒 Safe by design — pre-flight checks (valid git repo, no overlaps, no path traversal) before touching disk;
dryRunpreviews without writing.🪶 Stateless — nothing persisted; uses your logged-in
claudeCLI (no API key needed).
Requirements
Bun 1.3+
git2.x (forscaffold_worktrees)The
claudeCLI, logged in (fordecompose_into_plans)Claude Code or any MCP client
Installation
From npm — nothing to clone:
claude mcp add batuta -- bunx --bun @vorluno/batuta-mcpFrom source — if you want to change it:
git clone https://github.com/vorluno/batuta-mcp.git
cd batuta-mcp
bun install
claude mcp add batuta -- bun run /absolute/path/to/batuta-mcp/src/index.tsConfiguration
Any MCP client works. The mcpServers entry:
{
"mcpServers": {
"batuta": {
"command": "bun",
"args": ["run", "/absolute/path/to/batuta-mcp/src/index.ts"]
}
}
}For Claude Code, claude mcp add (above) writes this for you. For Warp or Cursor, paste the snippet into their MCP settings.
Tools
Tool | Description |
|
|
|
|
|
|
Typical flow
decompose_into_plans→ plans with disjoint boundaries.check_boundary_overlaps→ confirmok: true(or adjust).scaffold_worktrees→ creates the worktrees; open each in its own terminal/tab and paste itssuggestedPrompt.
Development
bun test # full suite
bunx tsc --noEmit # type-checkBuilt test-first across 10 TDD tasks with per-task and whole-branch review.
Contributing and security
Read CONTRIBUTING.md first — its first line tells you whether your pull request will be considered. Vulnerabilities go to security@vorluno.dev, never to an issue: see SECURITY.md, where the 72-hour acknowledgement is the one response time we commit to.
License
Apache-2.0 © 2026 Vorluno. See NOTICE.
Up to and including 0.1.0 this was MIT. Those releases stay MIT — a licence already granted cannot be withdrawn. From 0.2.0 on it is Apache-2.0, which grants patent rights explicitly.
Built by Vorluno — a software studio from Panamá 🇵🇦
Part of the mcp-s family of MCP servers.
Looking for live coordination between sessions instead of separation? See agora.
Available Tools
3 toolscheck_boundary_overlapsCheck boundary overlapsC
Pure check: do any plans share file boundaries? Returns overlaps and ok.
Inputs: plans (required). Returns: overlaps, ok
decompose_into_plansDecompose into plansB
Split a brain dump into 2-5 plans with DISJOINT file boundaries (auto-corrects overlaps once). Returns plans, overlapsResolved, attempts.
Inputs: brainDump (required), projectHint, repoPath. Returns: plans, overlapsResolved, attempts
scaffold_worktreesScaffold git worktreesA
Validate (git repo, no overlaps, safe paths) then create a git worktree per plan and return a ready-to-paste prompt per plan. Set dryRun to preview without touching disk.
Inputs: repoPath (required), plans (required), dryRun. Returns: results
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: checking overlaps, decomposing input, and scaffolding worktrees. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, making them predictable and easy to understand.
Three tools is exactly right for the focused domain of plan decomposition and worktree setup. The scope is well-defined.
The tool set covers the full workflow: validation (check), creation (decompose), and execution (scaffold). There are no obvious gaps for its stated purpose.
Maintenance
Related MCP Connectors
MCP server for generating rough-draft project plans from natural-language prompts.
A MCP server built for developers enabling Git based project management with project and personal…
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for managing a project backlog as Markdown files in Git, enabling AI agents to read, create, and update tasks programmatically.2MIT
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server for file-based task management and multi-agent team orchestration, enabling creation, completion, and reassignment of tasks across teams.-
- AlicenseAqualityDmaintenanceA filesystem-based MCP server for AI coding agents to coordinate work across git worktrees by claiming files, checking for conflicts, and logging progress without affecting the repository's git history.5MIT
- AlicenseAqualityBmaintenanceMCP server for Claude Code agents to manage persistent shared task boards with dependency graphs, atomic claims, and git-bound tasks.11MIT