imap-mcp
Related Servers
Alternatives to imap-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables read-only IMAP email access through MCP, including listing accounts and folders, searching messages, retrieving message bodies and attachments, and viewing threads without modifying mail state.MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to browse folders, list and search messages, read emails, and retrieve selected attachments through a private read-only MCP bridge with OAuth and safe HTML extraction.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to check, list, search, read, send, draft, and trash email in a single IMAP mailbox using standard IMAP and SMTP settings, with sending and trash moves enabled only when explicitly allowed.25 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to securely search multiple mailboxes, reconstruct email threads, and inspect attachments through read-only tools without altering mailbox state.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables read-only, sanitized access to Yahoo Mail through MCP, including email summaries, search, and folder listing.-
- AlicenseAqualityAmaintenanceEnables MCP clients to search, read, and manage a self-hosted mailbox over JMAP, including attachments with OCR, sending, drafts, and contacts.10365 npmMIT
TDQS
Scored across 6 tools
The six tools mostly target distinct resources: server info, mailboxes, single message, attachments, and two message listings. The only mild overlap is between list_messages and list_new_messages (both enumerate messages), but the descriptions clearly separate server-side filter paging from AiSeen-keyword tracking of unhandled mail.
All names follow a strict verb_noun snake_case pattern (get_server_info, get_attachments, get_message, list_mailboxes, list_messages, list_new_messages). The get_ vs list_ distinction maps cleanly to single-item vs collection retrieval.
Six tools is a reasonable, well-scoped set for a read-oriented IMAP surface, with no redundant entries. It is slightly thin if write operations were intended, but each tool clearly earns its place.
The read path is well covered: server capabilities, mailbox listing, message search/paging, single-message retrieval with thread context, new-message tracking, and attachment extraction. The main gaps are write-side operations (send, move, delete, flag changes), which appear intentionally omitted given the descriptions' emphasis on never altering read state.