Coordination mail for when your agents outnumber you

What it does

MCP Agent Mail is an HTTP-only FastMCP server that acts as a shared post office for coding agents. Each agent registers a memorable identity—think “GreenCastle”—and gets an inbox and outbox for GitHub-Flavored Markdown messages, complete with threaded conversations and search. It also lets agents declare advisory file reservations, or leases, on paths and globs to signal intent before editing, backed by Git for auditability and SQLite for indexing.

The interesting bit

The architecture treats agent coordination as asynchronous mail rather than real-time locking. Agents communicate across workstreams by sending messages and checking resources like resource://inbox/..., keeping coordination chatter out of the main context window while preserving a human-readable Git history of every instruction and lease. The README also promotes a broader “swarm” methodology—documented in its planning guide—for spinning up multiple Codex or Claude Code panes against a shared plan and task tracker.

Key highlights

• Agents get temporary-but-persistent identities and a searchable archive of messages, images, and threads.
• Exposed entirely through FastMCP tools and resources, targeting clients like Claude Code, Codex, and Gemini CLI.
• Advisory file leases reduce collisions; a pre-commit guard can optionally block conflicting exclusive reservations.
• Artifacts live in Git for human auditability; SQLite handles indexing and fast queries.
• The author pitches a productivity loop where one supervised hour of agent time supposedly yields ten to twenty parallel “human hours” when coordination is automated.

Caveats

• The project is under active development, and the README defers to a planning document for the full design, suggesting the implementation is still catching up to the vision.
• File reservations are strictly advisory—voluntary leases, not enforced locks—so conflict avoidance depends entirely on well-behaved agents.
• The installer automatically replaces the older Go-based Beads task tracker with a Rust reimplementation, which may disrupt existing workflows in that ecosystem.

Verdict

Try it if you are already juggling multiple agent CLI tools against the same repo and want a lightweight, mail-based way to partition work. Skip it if you run a single agent or prefer tight, synchronous orchestration over loose, asynchronous signaling.