Email MCP Server
Related Servers
Alternatives to Email MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server providing comprehensive email capabilities via IMAP and SMTP, enabling AI assistants to read, search, send, manage, schedule, and analyze emails across multiple accounts.49663 npmLGPL 3.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI models to read, search, and send emails via IMAP and SMTP protocols. It supports various providers like Gmail and Outlook, allowing for tasks such as retrieving unread messages, searching by sender, and managing mailbox folders.-
- AlicenseBqualityCmaintenanceAn MCP server that exposes IMAP operations as tools for AI assistants, enabling email management including listing mailboxes, reading, searching, moving, flagging emails, and creating drafts.721 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, manage, schedule, and analyze emails across multiple IMAP/SMTP accounts via MCP, with features like OAuth2, calendar extraction, analytics, and real-time email watching.461 npmLGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, manage, schedule, and analyze email across multiple IMAP/SMTP accounts through a single MCP server. Also supports drafts and templates, provider-aware labels and bulk operations, calendar extraction, real-time mailbox watching, and OAuth2 sign-in for Gmail and Microsoft 365.17 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, manage, schedule, and analyze email across multiple IMAP/SMTP accounts through MCP, including drafts and templates, provider-aware labels, bulk operations, real-time IMAP IDLE watching with AI triage, verification-code capture, calendar extraction, and analytics.17 npmISC
TDQS
Scored across 52 tools
Many tools target the same resource with overlapping actions—e.g., list_emails vs search_emails, get_email vs get_emails vs get_email_status, and mark_email vs bulk_action—so an agent could easily misselect despite detailed descriptions. Calendar/reminder tools (extract_calendar, analyze_email_for_scheduling, add_to_calendar) also have blurry boundaries. Some overlap exists but descriptions help.
Tool names consistently use snake_case and mostly follow a verb_noun pattern (list_emails, send_email, create_label, delete_mailbox). A few deviations like bulk_action (noun phrase) and list_scheduled (missing noun) are minor. The convention is predictable overall.
52 tools is far beyond the 3–15 typical for a well-scoped server and exceeds the 50+ threshold for extreme mismatch. Even accounting for the broad email+calendar+reminders scope, the surface is heavily overloaded with many niche configuration and diagnostic tools.
Email lifecycle is thoroughly covered: list/get/search/send/reply/forward/move/delete/mark/label/draft/schedule/templates. However, calendar and reminder operations lack update/delete tools, and account management (add/remove) is absent, leaving some dead ends.