Dicklesworthstone/mcp_agent_mail

What it solves

MCP Agent Mail provides a coordination layer for multiple AI coding agents working on the same project. It prevents agents from overwriting each other's work (race conditions) and ensures they don't miss critical context from parallel workstreams, removing the need for a human to manually relay messages between different agent tools.

How it works

The project implements a FastMCP server that acts as an asynchronous communication and signaling hub. It uses a dual persistence model: Git is used to store human-auditable markdown messages and inboxes/outboxes, while SQLite (with FTS5) handles fast indexing, search, and the management of "advisory file reservations" (leases) that signal an agent's intent to edit specific files or globs.

Who it’s for

Developers using multiple AI coding agents (such as Claude Code, Codex, Gemini CLI, or Factory Droid) across one or more codebases who need a shared fabric for identity, communication, and conflict avoidance.

Highlights

• Advisory File Reservations: Agents can lease files to signal intent and avoid stepping on each other.
• Asynchronous Messaging: Provides agents with memorable identities, searchable message history, and threaded conversations.
• getResource reads: Convenient resource URIs for agents to quickly read their inboxes or specific threads.
• Git-backed Audit Trail: Every instruction and message is stored as a human-readable artifact in Git.
• Beads Integration: Complements task planning tools like Beads by linking task IDs to mail threads and file reservations.