MCP Email Server
Related Servers
Alternatives to MCP Email Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceManages email accounts via IMAP/SMTP, enabling reading, searching, sending, replying, forwarding, and folder management with multi-user and OAuth support.221MIT
- AlicenseNot gradedqualityCmaintenanceEnables receiving and sending email via IMAP and SMTP across multiple accounts, with tools for listing, searching, reading, replying, and managing messages.MIT
- AlicenseNot gradedqualityDmaintenanceEnables sending and receiving emails through SMTP, IMAP, and POP3 protocols with support for attachments, HTML content, and email validation.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to search, read, send, move, mark, and delete email across multiple IMAP/SMTP accounts, with secure AES-256-encrypted credential storage and connection pooling.1,152 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, reply, forward, schedule, organize, and analyze email across multiple IMAP/SMTP accounts, with provider-aware labels, drafts, templates, and bulk operations. Additional capabilities include real-time IMAP IDLE watching with AI triage, verification-code capture, calendar extraction, analytics, and optional Streamable HTTP or OAuth2 access.21 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to search, read, send, reply, forward, organize, and bulk-delete emails across multiple IMAP and SMTP mailboxes with AES-256-encrypted credential storage and connection pooling. Supports 15+ pre-configured providers including Gmail, Outlook, Yahoo, and iCloud through a web-based setup wizard.1,152 npmMIT
TDQS
Scored across 21 tools
Most tools target distinct resource+action pairs, and the descriptions proactively clarify overlaps (e.g., mark_emails_as_read is noted as the workflow equivalent of set_email_flags adding \Seen). However, save_to_mailbox vs save_draft, set_email_flags vs set_email_tags, and move_emails vs archive_emails have overlapping purposes that could still cause misselection in edge cases.
The set is dominated by a consistent snake_case verb_noun pattern (list_emails_metadata, create_mailbox, send_email, move_emails, archive_emails). Minor deviations exist: download_attachment omits a resource prefix convention and email_command is a noun-ish outlier, but overall it's readable and predictable.
21 tools is on the heavy side for an email server; a few are arguably redundant (mark_emails_as_read duplicates set_email_flags behavior, save_to_mailbox and save_draft overlap, archive_emails is close to move_emails). Each still maps to a real operation, but the surface is broader than strictly necessary.
The surface covers the full email lifecycle: accounts, mailboxes, listing/reading, sending, forwarding, drafts, attachments, flags, tags, moving, archiving, and allowlists. Only modest gaps remain, such as no explicit search-by-sender/subject tool and no mailbox rename/delete, which are workarounds via listing and protocol commands.