@marlinjai/email-mcp
Related Servers
Alternatives to @marlinjai/email-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that enables email management (send, read, search, delete, etc.) via IMAP/SMTP, compatible with Gmail, Outlook, Yahoo, iCloud, and other standard mail servers.1139 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for unified email management that supports both Gmail and IMAP accounts via a single interface. It enables users to search across multiple accounts, list, read, send, and archive emails with integrated health monitoring and secure authentication.1MIT
- AlicenseNot gradedqualityBmaintenanceUnified email access via IMAP/SMTP, enabling reading, searching, sending, and deleting messages across multiple accounts through a single MCP server.9AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceMCP server for email management that enables reading, searching, drafting, replying to, and sending emails with thread-aware replies and draft-first safety, supporting Gmail API and IMAP/SMTP backends.-
- AlicenseAqualityBmaintenanceA high-fidelity IMAP/SMTP MCP server that enables reading, searching, and sending emails from providers like iCloud and Gmail, handling real-world IMAP quirks automatically.1578 PyPI2MIT
- AlicenseBqualityCmaintenanceUniversal IMAP/SMTP MCP server that works with any email provider, providing tools to read, search, send, and manage emails.10242 npm1MIT
TDQS
Scored across 36 tools
Most tools have clearly distinct resource+action targets, and batch variants are explicitly separated from single-item operations. Minor possible confusion exists between email_label and email_mark, or email_move and email_transfer, but the descriptions resolve the boundaries well.
All tools consistently use an email_ prefix and snake_case, making the set predictable. There is slight variation in compound ordering (email_draft_create vs. email_create_block_rule), but the convention remains readable throughout.
At 36 tools, the surface is heavy for an email server, with many batch twins and granular rule-management tools inflating the count. Each tool has a role, but the set would benefit from consolidation to reduce selection load.
The surface covers accounts, messages, threads, attachments, drafts, folders, labels/categories, batch operations, spam reporting, and forwarding/block rules. Minor gaps remain around folder rename/delete and fuller draft lifecycle operations such as deleting or sending an existing draft.