mailroom-mcp
Related Servers
Alternatives to mailroom-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read and organize mail, manage drafts, and perform broader mailbox operations under configurable read-only, draft-only, or full-access modes.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read, search, organize, draft, and send email across connected mailboxes with configurable access levels and auditable, undoable actions.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables software agents to read and manage their own mailboxes, inspect inbound messages, and request outbound email that remains pending until an owner approves it. Exposes these agent mail operations as remote MCP tools alongside a REST API.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI assistants to securely search multiple mailboxes, reconstruct email threads, and inspect attachments through read-only tools without altering mailbox state.Apache 2.0
- AlicenseAqualityCmaintenanceEnables MCP clients to search and read an IMAP mailbox, extract attachment text, reconstruct threads, and prepare plain-text drafts for review and manual sending, without sending, moving, deleting, modifying, or marking messages as read.6MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to manage multiple IMAP/SMTP mailboxes by listing folders, searching and reading messages, preparing Markdown drafts and replies, and sending only a draft the user has reviewed and confirmed.944 npmMIT
TDQS
Scored across 7 tools
Each tool has a distinct read target: conversation lists, a single conversation, pending approvals, audit trail, aggregate counts, KB questions, and redraft requests. There is mild overlap between list_conversations (filterable by status), list_pending_approvals, and inbox_summary, but the descriptions clearly separate list vs. queue vs. aggregate views.
Six of seven tools follow a consistent verb_noun pattern (list_conversations, get_conversation, list_pending_approvals, get_audit_trail, search_knowledge_base, request_redraft). inbox_summary breaks the pattern as a noun phrase, a minor but noticeable deviation.
Seven tools is well within the ideal 3-15 range and each maps to a distinct operator workflow step (triage, inspect, summarize, research, redraft). Nothing appears redundant or missing at the count level.
The surface covers listing, inspection, audit, summary, knowledge lookup, and redraft — a coherent read-and-request lifecycle with human approval intentionally excluded. Mutating operations like approve/reject/send are absent by design, so the only minor gap is the lack of a direct way to re-fetch or inspect a specific draft in isolation.