MailFathom
Related Servers
Alternatives to MailFathom
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI apps to search, read, summarise, thread, flag, file, draft, send and open attachments in IMAP and SMTP mailboxes, with each user signing in to their own mailbox. Self-hosted and bound to operator-configured mail servers, it keeps passwords sealed inside per-connection tokens so every tool call acts only as the mailbox owner.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceA self-hosted mail client MCP server that indexes email in PostgreSQL, enabling AI agents to search, move, mark, delete, and draft messages with bulk operations and attachment text extraction via OCR.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, reply, forward, schedule, and organize email across multiple IMAP/SMTP accounts, including drafts, labels, bulk operations, real-time mailbox watching, verification-code capture, calendar extraction, and analytics. It runs locally over stdio or as a networked Streamable HTTP service with OAuth2 sign-in and provider auto-detection.31 npmISC
- AlicenseAqualityDmaintenanceProvider-agnostic email MCP server that connects any IMAP mailbox to AI assistants, enabling email management through natural language.8AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceA self-hosted, multi-mailbox MCP server that exposes IMAP/SMTP operations as tools for AI agents, enabling email management like listing folders, reading, searching, sending, and moving messages via natural language.MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted server that connects AI assistants, including claude.ai as a custom connector, to an existing IMAP/SMTP or Microsoft Exchange mailbox. It enables searching and reading email, inspecting attachments in bounded chunks, and — when explicitly enabled for IMAP/SMTP — sending messages, managing drafts and organizing folders.MIT
TDQS
Scored across 20 tools
Each tool targets a distinct mail workflow: reading, searching, sending, replying, forwarding, draft lifecycle, contact management, flags, and outgoing message status. Even similar tools like list_emails and search_emails are clearly separated by summary listing versus ranked full-text search, and send_email versus send_draft by composing new output versus sending an existing draft.
All 20 tool names follow a consistent snake_case verb_noun convention: list_*, get_*, create_*, update_*, delete_*, send_*, save_*, forward_*, reply_to_*, cancel_*, set_*. The naming pattern makes the action and resource immediately clear across the entire set.
20 tools is on the heavier side, but each one maps to a distinct and necessary mail workflow rather than duplicating another. The set covers multiple coherent subdomains—reading, sending, drafts, contacts, and outgoing status—so the count feels purposeful rather than bloated.
Core mail lifecycle is well covered: read/search mail, fetch content, send/reply/forward, draft CRUD plus send, contact CRUD plus promotion, flag mutation, and outgoing message status/cancellation. Minor gaps exist, such as no way to delete or move synchronized emails and no way to attach new files to a freshly composed send, but agents can work around these or the gaps appear to be deliberate safety boundaries.