mailbox-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mailbox-mcpsend a message to dev-agent about the API endpoint changes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mailbox-mcp
MCP server for inter-agent mailbox communication. Structured API over the existing <repo>/.claude/{inbox,outbox}/*.md file convention used by Grygoriy's Claude-Code orchestration setup.
Status: Phase 1 in development.
Full spec: see SPEC.md.
Quick start
npm install
npm run build
npm start # runs the MCP server over stdioRegister in ~/.claude.json under mcpServers:
{
"mcpServers": {
"mailbox": {
"command": "node",
"args": ["C:\\Users\\Gree\\workspace\\tools\\mailbox-mcp\\dist\\index.js"]
}
}
}Restart Claude Code. Verify via /mcp — should list mailbox as connected.
Related MCP server: claude-presence
Tool surface (Phase 1)
mail_send(to, topic, body, [status, refs, reply_to, labels])— drop a mail into target agent's inboxmail_list(agent, folder, [status, since, labels, limit])— list mailsmail_get(id, agent, folder)— read full mailmail_reply(in_reply_to, body, [topic, to, parent_status, initial_status, ...])— reply + auto-flip parent. Topic defaults to the parent's — same conversation continues; pass an explicit topic only to fork the subject.mail_status(id, agent, folder, status)— flip status, audit-loggedmail_thread(root_id)— full thread tree
See SPEC.md for details.
Phase 2 (planned)
GitLab pipeline / MR watchers + templates + scheduled / conditional send. Separate background daemon.
Layout
src/
├── index.ts # MCP server entrypoint
├── types.ts # Mail types
├── config.ts # Agent enum + paths
├── tools/ # One file per tool
└── storage/ # File I/O, frontmatter, naming, auditNotes
mail_reply topic behavior — the reply's topic defaults to the parent's topic (same conversation continues). Pass an explicit topic only when the reply forks the subject. Previously the schema required topic; if a caller omitted it, the JS coerced undefined → the literal string "undefined" past the regex-only validator, producing filenames like 2026-07-07-1111-undefined.md and frontmatter with no topic: key — which mail_list then silently skipped as malformed. assertValidTopic now hard-rejects non-string / empty.
License
MIT — see LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/EllGree/mailbox-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server