Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Split a task into plans with disjoint file boundaries; scaffold a git worktree per plan.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"batuta": {
"command": "npx",
"args": [
"-y",
"@vorluno/batuta-mcp"
]
}
}
}Run this in your terminal
claude mcp add batuta -- npx -y @vorluno/batuta-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"batuta": {
"command": "npx",
"args": [
"-y",
"@vorluno/batuta-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"batuta": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@vorluno/batuta-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account vorluno, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
It's a stateless MCP server (stdio). No database, no daemon, no web UI — just three tools that compose:
fileBoundaries don't overlap (auto-corrects once if they do).git worktree per 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.
git worktree per plan, with a ready-to-paste prompt.dryRun previews without writing.claude CLI (no API key needed).git 2.x (for scaffold_worktrees)claude CLI, logged in (for decompose_into_plans)From npm — nothing to clone:
claude mcp add batuta -- bunx --bun @vorluno/batuta-mcp
From 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.ts
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.
| Tool | Description |
|---|---|
decompose_into_plans | { brainDump, projectHint?, repoPath? } → { plans, overlapsResolved, attempts }. Splits the work into plans with disjoint boundaries (auto-corrects overlaps once). |
check_boundary_overlaps | { plans } → { overlaps, ok }. Pure check: do any plans share files? |
scaffold_worktrees | { repoPath, plans, dryRun? } → { results }. Pre-flight, then git worktree add per plan + a ready-to-paste prompt. |
decompose_into_plans → plans with disjoint boundaries.check_boundary_overlaps → confirm ok: true (or adjust).scaffold_worktrees → creates the worktrees; open each in its own terminal/tab and paste its suggestedPrompt.bun test # full suite
bunx tsc --noEmit # type-check
Built test-first across 10 TDD tasks with per-task and whole-branch review.
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.
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](https://vorluno.dev) — 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.