mailbox-mcp
MCP server for inter-agent mailbox communication using file-based mailboxes in .claude directories.
README
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 stdio
Register 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.
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, audit
Notes
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.