MCP Email Server
Related Servers
Alternatives to MCP Email Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceManages email accounts via IMAP/SMTP, enabling reading, searching, sending, replying, forwarding, and folder management with multi-user and OAuth support.222MIT
- 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,009 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.31 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,009 npmMIT
TDQS
Scored across 21 tools
Most tools target clearly distinct resource+action pairs (metadata vs. content vs. attachment vs. mailbox). A few overlaps create mild confusion: save_to_mailbox vs. save_draft (both compose unsent mail), mark_emails_as_read vs. set_email_flags (explicitly the same \Seen effect), and archive_emails vs. move_emails, though the descriptions do distinguish them.
Strong, predictable verb_noun snake_case throughout: list_*, get_*, send_*, set_*, save_*, delete_*, move_*, archive_*, create_*, download_*. The only notable deviation is email_command (noun_verb escape hatch) and the get_* vs. download_* split for attachments, but it remains readable and mostly uniform.
21 tools is on the heavy side for an email server and lands in the borderline 16-25 band. Each tool does map to a real operation (accounts, allowlists, tags, mailboxes, flags, drafts, attachments, protocol escape), but the surface feels broad and could be consolidated (e.g. save_draft into save_to_mailbox).
The domain is well covered: read metadata/content/attachments, send, forward, drafts, flags, tags, move/archive/delete, mailbox list/create, account and allowlist inspection, plus a protocol escape hatch. Minor gaps exist around mailbox lifecycle (rename/delete folder not offered) and there is no dedicated search tool, but email_command can work around these.