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.2MIT
- 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.8 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 gradedqualityCmaintenanceMCP 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
- FlicenseNot gradedqualityBmaintenanceLocal MCP server for personal Outlook.com/Hotmail/Live accounts, enabling email triage, folder management, bulk operations, and newsletter unsubscribe via Microsoft Graph.-
TDQS
Scored across 31 tools
The same core operations (send, search, get, delete, move, update flags) are repeated across ews_, graph_, imap_, and smtp_ tools, and the IMAP delete/move/flag tools have overlapping single, bulk, and search-and-act variants. The protocol prefixes and provider notes help, but an agent still has to determine which of several similarly named tools applies to a given task and account.
Most tools cleanly follow a protocol_verb_noun pattern (ews_get_message, imap_create_mailbox, smtp_forward_message). A few outliers like list_all_accounts, imap_list_accounts, imap_mailbox_status, and get_setup_guide break the pattern, but they are easy to understand and not chaotic.
At 31 tools, the surface is heavier than necessary, largely because the same operations are reimplemented per protocol and augmented with bulk/search-and-act variants that could be consolidated. The multi-protocol scope justifies some breadth, but the number will tax an agent's tool-selection decisions.
The set covers the full email lifecycle: send/reply/forward, search/read, move/copy/delete, flag updates, attachment retrieval, mailbox CRUD, account verification, and setup guidance. No major dead-end operation appears to be missing for a mail-focused MCP server.