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.8MIT
- 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.3MIT
- AlicenseNot gradedqualityCmaintenanceCross-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.38 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 gradedqualityDmaintenanceMCP 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
- FlicenseAqualityCmaintenanceLocal MCP server for personal Outlook.com/Hotmail/Live accounts, enabling email triage, folder management, bulk operations, and newsletter unsubscribe via Microsoft Graph.21-
TDQS
Scored across 37 tools
The protocol-prefixed names help distinguish backends, but send/reply/forward functionality is duplicated across smtp_, ews_, graph_ and draft_ variants, and list_all_accounts vs imap_list_accounts, or imap_get_message vs imap_get_message_raw, invite misselection. Descriptions clarify intent, but an agent must reason carefully about account capabilities before choosing.
A clear protocol_action_resource pattern (imap_get_message, smtp_send_message, ews_search_messages) dominates and is predictable. Minor deviations like list_all_accounts, get_setup_guide, and resource-first draft_create keep it from being fully uniform.
37 tools is heavy for what is fundamentally a send/read/search/manage domain, and much of the bulk comes from near-duplicate per-protocol send and search tools. The surface exceeds what most agents will comfortably navigate.
Coverage is strong: send/reply/forward, drafts lifecycle, search (including all-mailbox and search-and-act), bulk flag/move/delete, mailbox management, attachments, and flags are all present. Only minor gaps like attachment handling limited to IMAP keep it from a 5.