mail-mcp
Related Servers
Alternatives to mail-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceLocal MCP server for multi-account IMAP/SMTP email (iCloud + Gmail via app-specific passwords). Never marks mail read. Cross-folder search, idempotent sends, TLS verified.835 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceMulti-account IMAP/SMTP email MCP server with 22 tools — read, send, search, organize, thread, attachments, and batch operations. Features connection pooling, rate limiting, retry with backoff, and OAuth2 device-code flow. Written in Go.4MIT
- AlicenseNot gradedqualityDmaintenanceCross-platform MCP server and CLI for email operations, including send, read, search, and contact management, compatible with Gmail, Outlook, Yahoo, and any IMAP/SMTP providers.29 npm1MIT
- FlicenseAqualityDmaintenanceA lightweight MCP server for personal Microsoft Outlook/Hotmail accounts, enabling email search, reading, attachment management, and folder operations via Microsoft Graph API with OAuth device-code flow.61-
- AlicenseNot gradedqualityBmaintenanceMCP server providing read and send access to a single IMAP/SMTP mailbox over Streamable HTTP with GitHub OAuth authentication, featuring recipient allowlists for security, email reading/searching/threading, attachments, drafts, folder management, and sending/reply tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, read, draft, move and flag mail in self-hosted IMAP mailboxes over MCP Streamable HTTP, protected by OAuth 2.1 with per-client, per-folder and per-operation rules, encrypted credentials and a full audit log. A Go sidecar handles header reads with caching, while structured errors, request ids and verified write outcomes keep unattended operation reliable.MIT
TDQS
Scored across 37 tools
Several tool clusters overlap heavily: smtp_send_message, ews_send_message, graph_send_message, and draft_send all perform sends, while imap_search_messages, ews_search_messages, and imap_search_all_mailboxes overlap on search. Protocol prefixes and descriptions help, but correct selection depends on knowing account capabilities, creating real misselection risk.
Names are consistently snake_case and mostly follow a protocol/resource_action pattern such as imap_get_message, smtp_send_message, and draft_update. Minor deviations exist in generic tools like list_all_accounts and get_setup_guide, which lack the otherwise common protocol prefix.
With 37 tools, the surface is well above the typical 3-15 range and feels heavy even for a multi-provider mail server. Many near-duplicate operations exist across IMAP, SMTP, EWS, and Graph, increasing tool-selection burden.
Coverage is broad: account discovery and verification, mailbox CRUD, message search/get/raw/attachments, copy/move/delete, flags, bulk operations, drafts, and send/reply/forward flows are present. Minor gaps remain, such as reply/forward support only via SMTP rather than EWS or Graph.