MCP Emails
Related Servers
Alternatives to MCP Emails
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects any IMAP/SMTP mailbox to AI agents via MCP, enabling email read, search, send, reply, and management through natural language.8 npmMIT
- AlicenseAqualityDmaintenanceProvider-agnostic email MCP server that connects any IMAP mailbox to AI assistants, enabling email management through natural language.8AGPL 3.0

commune-mcpofficial
AlicenseAqualityCmaintenanceGive Claude (or any MCP client) a real email inbox and SMS. Your AI agent can read and send email, manage inboxes, track delivery, and handle SMS.271Apache 2.0- AlicenseNot gradedqualityBmaintenanceConnects existing IMAP/POP3/SMTP email accounts to AI assistants via MCP, with a web client for managing accounts and downloading attachments.7 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to read and send email, handle attachments and manage calendar invitations through their own IMAP/SMTP mailboxes, with per-mailbox sender and recipient allow lists and automatic HTML-to-Markdown conversion. It runs as a single self-hosted Docker container, exposing the same tools over MCP and REST.1512MIT
- AlicenseAqualityAmaintenanceConnect all your email accounts to your AI agent — not just one. AnyMail MCP is a local MCP server that gives an agent full read/send/organize/delete access across multiple Gmail accounts at once, over IMAP/SMTP.2620 npm4MIT
TDQS
Scored across 23 tools
Most tools are clearly separated by resource (inbox, email, folder, draft, schedule, signature, automation, contact, approval, bulk). The main ambiguity is email_organize vs email_search_and_move, but the descriptions explicitly call out the distinction (id-based vs filter-based), and email_delete vs bulk_execute are also clearly separated by destructive scope.
Tool names mostly follow a noun_verb or verb_noun pattern (inbox_list, email_read, email_organize, folder_list, draft_list, signature_get, automation_read, contact_search, approval_review, bulk_execute). Minor deviations: 'folder' and 'draft' are bare nouns for CRUD tools, and 'schedule' is a verb while 'schedule_list' is noun_verb, but the pattern is still readable and predictable.
23 tools is on the higher end but justified for a full email server covering inboxes, messages, folders, drafts, scheduling, signatures, automations, contacts, approvals, and bulk operations. Each tool has a distinct role, though a few could be merged (e.g., approval_review/decide/update/schedule could be one tool with actions).
The surface covers the full email lifecycle: read, search, compose, send, reply, forward, organize, delete, drafts, scheduling, signatures, folders, automations, contacts, approvals, and bulk operations. The only minor gap is no direct tool for listing sent mail, but email_read with folder='Sent' covers that.