Skip to main content
Glama
fathomise

MailFathom

by fathomise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Related Servers

Alternatives to MailFathom

No user-submitted related servers found.

    Related Servers

    • mailindex-mcp

      alexanderkrauck
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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

    • io.github.p-w-4-z/inbox-mcp

      p-w-4-z
      A
      license
      A
      quality
      D
      maintenance
      Provider-agnostic email MCP server that connects any IMAP mailbox to AI assistants, enabling email management through natural language.
      8
      AGPL 3.0

    • mail-mcp

      MauricioPerera
      A
      license
      Not graded
      quality
      B
      maintenance
      A 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

    • mailbridge

      marcocavanna
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that gives an AI assistant access to IMAP/SMTP mailboxes to read, search, organize, draft, and send email, with local mirroring and full-text search, no third-party data path, and credentials stored only in the macOS Keychain.
      17 npm
      MIT

    • imaplane

      danb0nd
      A
      license
      Not graded
      quality
      B
      maintenance
      Local IMAP control plane for AI agents, providing an HTTP API and MCP tools to read, search, move, flag, and optionally send emails, with support for iCloud and generic IMAP accounts.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 20 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources