mailbox-mcp
Related Servers
Alternatives to mailbox-mcp
- FlicenseAqualityDmaintenanceAn MCP server for semantic search and retrieval of indexed Slack messages stored in Qdrant using Cohere reranking via AWS Bedrock. It enables users to search through Slack history, retrieve full message threads, and access channel or user statistics through natural language.5-
Related Servers
- AlicenseNot gradedqualityBmaintenanceHosted remote MCP server that lets AI agents compose, price, send, and track real physical letters worldwide.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI agents create reviewable physical mail drafts, validate quotes, and pay for postage via MPP or x402 protocols.2MIT
- AlicenseNot gradedqualityCmaintenanceAn open-source MCP server for sending physical mail (letters, postcards, certified mail) directly from AI agents, with per-piece payment and no account signup needed.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to prepare, price, review, pay for, and send real physical letters and postcards via a hosted MCP server.-
- AlicenseBqualityBmaintenanceOfficial MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.100837 npm1MIT

Escouade Mailofficial
AlicenseNot gradedqualityCmaintenanceProvides a hosted remote MCP server that lets AI agents create and use their own email address to send, receive, verify, and reply to messages.MIT
TDQS
Scored across 55 tools
The surface contains two parallel inbound families (forwarded-email inbound mail vs. physical inbound items) with near-identical names (list_inbound_mail vs. list_inbound_items, get_inbound_mail vs. get_inbound_item), plus ten deprecated *_agent_inbox_* aliases that duplicate what the inbound tools now do. Webhook handling is also split between update_webhook and the create/update_webhook_endpoint family, leaving agents to guess which is authoritative.
Almost everything follows a predictable snake_case verb_noun pattern (list_webhook_endpoints, create_batch_mail, get_outbound_mail, rotate_webhook_endpoint_secret). Minor deviations exist: propose_mailbox_md_edit inverts noun ordering and update_webhook lacks the _endpoint suffix used by its siblings.
55 tools is very heavy for a mailbox service, and roughly ten of them are explicitly deprecated alias-window tools that add clutter without new capability. The domain is genuinely broad (outbound, batch, webhooks, inbound, facility messaging), but the set is well past the point where an agent can hold it in working memory.
Coverage is broad — mailbox identity, outbound lifecycle (send/list/get/cancel/test), batch lifecycle (create/estimate/confirm/get/proof/advance), webhooks (CRUD/test/deliveries/replay/rotate), inbound items, quoting, actions, threads, and usage. Remaining gaps are minor (e.g., no explicit delete for webhook endpoints or outbound records), so an agent can complete most workflows.