agent-maillisted

# MCP Agent Mail A mail-like coordination layer for coding agents exposed as an HTTP-only FastMCP server. Provides memorable identities, inbox/outbox, file reservation leases, contact policies, searchable message history, and Human Overseer messaging. Backed by Git (human-auditable artifacts) and SQLite (fast queries with FTS5). ## Why This Exists Without coordination, multiple agents: - Overwrite each other's edits or panic on unexpected diffs - Miss critical context from parallel workstreams - Require humans to relay messages between tools Agent Mail solves this with: - Memorable identities (adjective+noun names like "GreenCastle") - Advisory file reservations to signal editing intent - Threaded messaging with importance levels and acknowledgments - Pre-commit guard to enforce reservations at commit time - Human Overseer for direct human-to-agent communication ## Starting the Server ```bash # Quickest way (alias added during install) am # Or manually cd ~/projects/mcp_agent_mail ./scripts/run_server_with_token.sh ``` Default: `http://127.0.0.1:8765` Web UI for humans: `http://127.0.0.1:8765/mail` ## Core Concepts ### Projects Each working directory (absolute path) is a project. Agents in the same directory share a project namespace. Use the same `project_key` for agents that need to coordinate. ### Agent Identity Agents register with adjective+noun names (GreenCastle, BlueLake). Names are unique per project, memorable, and appear in inboxes, commit logs, and the