mcp_agent_mail

Name: mcp_agent_mail
Author: dicklesworthstone

bydicklesworthstone· 102 skills

Stars

2.0k

Forks

216

How to install mcp_agent_mail?

dicklesworthstone/mcp_agent_mail

$npx -y skills add dicklesworthstone/mcp_agent_mail --skill mcp_agent_mail

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Use this skill

Run `npx skills use "https://github.com/dicklesworthstone/mcp_agent_mail" --skill "dicklesworthstone/mcp_agent_mail"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the whole pack

Use the skills in "https://github.com/dicklesworthstone/mcp_agent_mail" that are relevant to the current task. Run `npx skills add "https://github.com/dicklesworthstone/mcp_agent_mail"` and select the relevant skills, then follow their instructions.

Files · 1

View on GitHub

SKILL.md

1	# MCP Agent Mail
2
3	![Agent Mail Showcase](screenshots/output/agent_mail_showcase.gif)
4
5	> "It's like gmail for your coding agents!"
6
7	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.
8
9	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).
10
11	Status: Under active development. The design is captured in detail in `docs/planning/project_idea_and_guide.md` (start with the original prompt at the top of that file).
12
13	## Why this exists
14
15	Modern projects often run multiple coding agents at once (backend, frontend, scripts, infra). Without a shared coordination fabric, agents:
16
17	- Overwrite each other's edits or panic on unexpected diffs
18	- Miss critical context from parallel workstreams
19	- Require humans to "liaison" messages across tools and teams
20
21	This project provides a lightweight, interoperable layer so agents can:
22
23	- Register a temporary-but-persistent identity (e.g., GreenCastle)
24	- Send/receive GitHub-Flavored Markdown messages with images
25	- Search, summarize, and thread conversations
26	- Declare advisory file reservations (leases) on files/globs to signal intent
27	- Inspect a directory of active agents, programs/models, and activity
28
29	It's designed for: FastMCP clients and CLI tools (Claude Code, Codex, Gemini CLI, Factory Droid, etc.) coordinating across one or more codebases.
30
31	## From Idea Spark to Shipping Swarm
32
33	If a blank repo feels daunting, follow the field-tested workflow we documented in `docs/planning/project_idea_and_guide.md` (“Appendix: From Blank Repo to Coordinated Swarm”):
34
35	- Ideate fast: Write a scrappy email-style blurb about the problem, desired UX, and any must-have stack picks (≈15 minutes).
36	- Promote it to a plan: Feed that blurb to GPT-5 Pro (and optionally Grok4 Heavy / Opus 4.1) until you get a granular Markdown plan, then iterate on the plan file while it’s still cheap to change. The Markdown Web Browser sample plan shows the level of detail to aim for.
37	- Codify the rules: Clone a tuned `AGENTS.md`, add any tech-specific best-practice guides, and let Codex scaffold the repo plus Beads tasks straight from the plan.
38	- Spin up the swarm: Launch multiple Codex panes (or any agent mix), register each identity with Agent Mail, and have them acknowledge `AGENTS.md`, the plan document, and the Beads backlog before touching code.
39	- Keep everyone fed: Reuse the canned instruction cadence from the tweet thread or, better yet, let the commercial Companion app’s Message Stacks broadcast those prompts automatically so you never hand-feed panes again.
40
41	Watch the full 23-minute walkthrough (https://youtu.be/68VVcqMEDrs?si=pCm6AiJAndtZ6u7q) to see the loop in action.
42
43	## Productivity Math & Automation Loop
44
45	One disciplined hour of GPT-5 Codex—when it isn’t waiting on human prompts—often produces 10–20 “human hours” of work because the agents reason and type at machine speed. Agent Mail multiplies that advantage in two layers:
46
47	1. Base OSS server: Git-backed mailboxes, advisory file reservations, Typer CLI helpers, and searchable archives keep independent agents aligned without babysitting. Every instruction, lease, and attachment is auditable.
48	2. Companion stack (commercial): The iOS app + host automation can provision, pair, and steer heterogeneous fleets (Claude Code, Codex, Gemini CLI, Factory Droid, etc.) from your phone using customizable Message Stacks, Human Overseer broadcasts, Beads awareness, and plan editing tools—no manual tmux choreography required. The automation closes the loop by scheduling prompts, honoring Limited Mode, and enforcing Double-Arm confirmations for destructive work.
49
50	Result: you invest 1–2 hours of human supervision, but dozens of agent-hours execute in parallel w

6 picks

Type

Run `npx skills use "https://github.com/dicklesworthstone/mcp_agent_mail" --skill "dicklesworthstone/mcp_agent_mail"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.

Use the skills in "https://github.com/dicklesworthstone/mcp_agent_mail" that are relevant to the current task. Run `npx skills add "https://github.com/dicklesworthstone/mcp_agent_mail"` and select the relevant skills, then follow their instructions.

mcp_agent_mail

How to install mcp_agent_mail?

Related

mcp_agent_mail

How to install mcp_agent_mail?

Related