# Dicklesworthstone/mcp_agent_mail

Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite

Repository: https://github.com/Dicklesworthstone/mcp_agent_mail
Canonical: https://ross.abutalabs.com/products/mcp_agent_mail
Language: Python
License: NOASSERTION
License Family: other
Topics: ai-agents, coordination, fastmcp, mcp, python
Last push: 2026-08-26T07:14:14+00:00

## Health v2 (maintenance only)
Score: 77/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 80, longevity 22
- inputs: {"age_days": 314, "days_push": 7, "days_rel": 139, "gap_med": 0.0, "n_releases_24m": 9}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2114, forks 225 (observed 2026-08-28T04:06:15.717857+00:00)

## What it is
MCP Agent Mail is an asynchronous coordination layer for AI coding agents, exposed as an HTTP-only FastMCP server. It gives agents persistent identities, inboxes, searchable threaded messages, and advisory file reservation leases, backed by Git and SQLite.

## Use cases
- coordinate multiple AI coding agents working on the same codebase
- give coding agents identities and inboxes to exchange messages
- prevent agents from overwriting each other's edits with file leases
- search and summarize conversation threads between agents
- run a directory of active agents and their activity
- let Claude Code, Codex, or Gemini CLI agents communicate asynchronously

## When to choose
- you run multiple AI coding agents in parallel on shared repositories
- you want human-auditable, Git-backed agent communication artifacts
- you need advisory file reservations to signal change intent between agents
- you use MCP-compatible clients and want a lightweight self-hosted coordination fabric

## When to avoid
- you need hard mutual-exclusion locking rather than advisory leases
- you want a fully managed cloud service rather than self-hosting
- your agents operate in isolation with no need for inter-agent messaging
- you require a non-Python or non-MCP integration environment

## Facets
- artifact type: service
- maturity: active
- function: mcp, message-queue, search-engine, developer-tools
- domain: developer-tools, self-hosted
- platform: python, self-hosted, cli
- tags: fastmcp, agent-coordination, multi-agent, file-leases, sqlite, git-backed, inbox, coding-agents, ai-agents, automation

## Member repositories
- Dicklesworthstone/mcp_agent_mail (main) score 77

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:15.717857+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:53:28.352527+00:00, confidence not recorded.
  - readme: https://github.com/Dicklesworthstone/mcp_agent_mail (fetched 2026-08-28T04:06:15.717857+00:00, sha c8358e78d047)
- Data as of 2026-08-30T08:39:29.467469+00:00.