Email MCP Server
Related Servers
Alternatives to Email MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to email accounts via IMAP/SMTP, enabling reading, searching, sending, and organizing emails with features like smart drafts, scheduling, and attachment handling.92 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, search, send, and organize email over IMAP and SMTP for providers such as Gmail, Yahoo, iCloud, Zoho, Fastmail, and custom domains, with tools for attachments, drafts, templates, scheduling, and safe mailbox management.282 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to read, search, compose, and send emails by connecting to any IMAP/SMTP provider. It supports comprehensive mailbox management, including draft handling and message deletion, directly through natural language.10206 npm11MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, send, organize, and search emails across multiple IMAP/SMTP mailboxes.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to connect to any email provider via IMAP/SMTP, supporting account management and email operations like listing, sending, and marking emails.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage multiple email accounts over IMAP and SMTP — searching, reading, sending, replying, forwarding, moving, marking, and bulk-deleting messages, plus folder management and unread counts — with AES-256-encrypted credential storage, connection pooling, and a web-based setup wizard covering 15+ providers.931 npmMIT
TDQS
Scored across 28 tools
Most tools target a distinct message, thread, label, or mailbox action, and descriptions clarify differences between send/reply, archive/trash/delete, and digest/triage/cleanup. A few adjacent automation helpers such as email_triage and email_cleanup could still be confused if descriptions are skimmed.
The email_ prefix is consistent and all names use snake_case, but the verb+noun pattern is not followed consistently. Tools like email_inbox, email_profile, email_labels, email_digest, and email_contacts are noun-style, while email_list_drafts, email_mark_read, and email_create_label are verb-style, making the naming mixed but still readable.
28 tools exceeds the 25+ threshold for too many, and several compound helpers such as email_digest, email_triage, email_cleanup, email_cold_campaign, and email_follow_up could be composed from the basic primitives. The set feels overpopulated even though each tool has a distinct role.
Core email workflows are well covered: search, read, send, reply, drafts, labels, flags, archive, trash, and delete all have dedicated tools. Minor gaps remain, such as no draft editing, no label deletion, and no attachment upload or forward, but agents can work around these.