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 gradedqualityAmaintenanceHosted remote MCP server that lets AI agents compose, price, send, and track real physical letters worldwide.1MIT
- AlicenseNot gradedqualityFmaintenanceMCP server that lets AI agents create reviewable physical mail drafts, validate quotes, and pay for postage via MPP or x402 protocols.2MIT
- AlicenseNot gradedqualityBmaintenanceAn 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.-
- AlicenseBqualityAmaintenanceOfficial MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.100513 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for Sendook - an AI email communication platform. Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.16MIT
TDQS
Scored across 45 tools
The set includes many deprecated aliases (e.g. list_agent_inbox vs search_inbound_items, get_agent_inbox_sources vs get_inbound_item) plus overlapping inbound readers and two webhook update tools, so agents must carefully read deprecation notes to choose correctly. Distinct resources exist, but the duplicated old/new paths create real misselection risk.
Nearly all names use snake_case verb_noun (list_*, get_*, create_*, update_*), which is predictable. Minor deviations like update_webhook versus update_webhook_endpoint and get_mailbox versus get_mailbox_md keep it from being perfect.
45 tools is far above the ideal range, and much of the excess comes from eleven deprecated aliases that remain served. The useful surface is broad but inflated, making this feel heavy and maintenance-prone.
Core lifecycle coverage is good: inbound search/read/pages/actions/quotes, outbound send/list/get/cancel/test/advance, webhook create/list/update/test/deliveries/replay, facility messaging, usage, and MAILBOX.md reads/proposals. Gaps include no delete_webhook_endpoint and no outbound update, but agents can mostly work around them.