iflow-mcp_dicklesworthstone_mcp-agent-mail

# MCP Agent Mail  > "It's like gmail for your coding agents!" A mail-like coordination layer for coding agents, exposed as an HTTP-only FastMCP server. It gives agents memorable identities, an inbox/outbox, searchable message history, and voluntary file reservation "leases" to avoid stepping on each other. Think of it as asynchronous email + directory + change-intent signaling for your agents, backed by Git (for human-auditable artifacts) and SQLite (for indexing and queries). Status: Under active development. The design is captured in detail in `project_idea_and_guide.md` (start with the original prompt at the top of that file). ## Why this exists Modern projects often run multiple coding agents at once (backend, frontend, scripts, infra). Without a shared coordination fabric, agents: - Overwrite each other's edits or panic on unexpected diffs - Miss critical context from parallel workstreams - Require humans to "liaison" messages across tools and teams This project provides a lightweight, interoperable layer so agents can: - Register a temporary-but-persistent identity (e.g., GreenCastle) - Send/receive GitHub-Flavored Markdown messages with images - Search, summarize, and thread conversations - Declare advisory file reservations (leases) on files/globs to signal intent - Inspect a directory of active agents, programs/models, and activity It's designed for: FastMCP clients and CLI tools (Claude Code, Codex, Gemini CLI, etc.) coordinating across one or more codebases. ## From Idea Spark to Shipping Swarm If a blank repo feels daunting, follow the field-tested workflow we documented in `project_idea_and_guide.md` (“Appendix: From Blank Repo to Coordinated Swarm”): - **Ideate fast:** Write a scrappy email-style blurb about the problem, desired UX, and any must-have stack picks (≈15 minutes). - **Promote it to a plan:** Feed that blurb to GPT-5 Pro (and optionally Grok4 Heavy / Opus 4.1) …