mailbox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mail_sendA | Send a brief/message to another agent's inbox. Writes a YAML-frontmatter markdown file to /.claude/inbox/-.md atomically. Caller identity comes from MAILBOX_MCP_AGENT_ID env var (default 'workspace'). Use this instead of writing files manually — it enforces naming, frontmatter, and audit. |
| mail_getA | Fetch a single mail by id from a given agent's folder. Returns full metadata + markdown body + absolute path. |
| mail_listA | List mails in a target agent's inbox or outbox. Filters: status, since (ISO date), labels (any-match), limit (default 100). Sorted newest-first. |
| mail_replyA | Reply to a mail. Finds parent in the CALLER's own inbox or outbox (use mail_send if you need to reply across agents), sends the reply with |
| mail_statusB | Change a mail's status. Validates the state-machine transition (open ↔ holding → done/superseded; done and superseded are terminal). Atomic write + audit entry. |
| mail_threadA | Walk the reply_to graph rooted at the given mail. Returns root + descendants in breadth-first order with depth annotation. Scans all known agents' folders — expensive but complete. |
| mail_migrateA | Backfill |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: retrieving specific mails, listing mails, migrating legacy files, replying to mails, sending new mails, changing status, and traversing threads. No two tools overlap in functionality.
All tool names follow the consistent pattern 'mail_<verb>' with lowercase snake_case verbs (get, list, migrate, reply, send, status, thread). The naming is perfectly uniform.
7 tools is well-scoped for a mailbox server. The set covers the essential operations without being excessive. Each tool serves a distinct and necessary function.
The tool surface covers core mailbox operations: fetching, listing, sending, replying, status management, and thread traversal. Minor gaps exist (e.g., no direct deletion), but status updates (done/superseded) effectively serve as archival, so the surface is mostly complete.