Skip to main content
Glama
adjurtime

163 Mail MCP

by adjurtime

Related Servers

Alternatives to 163 Mail MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Local 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.
      8
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI agents permission-gated, audit-logged access to private email providers (Proton Mail via Bridge and plain IMAP), running locally with OAuth-based authentication and human-controlled escalation for destructive operations.
      66
      60 npm
      11
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted Gmail gateway MCP server that enables searching and fetching emails from multiple authorized Gmail mailboxes via a single backend authorization boundary.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      A private, single-user MCP server that unifies Gmail, Microsoft 365/Outlook, and IMAP mailboxes for LLMs to search and read emails live, without storing or caching mailbox contents.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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
    • F
      license
      A
      quality
      C
      maintenance
      Local-first MCP server for agents that need to work across multiple Gmail and Microsoft 365 accounts without cloud token storage.
      6
      -

    TDQS

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools are clearly distinct: reading, sending, trashing, moving, search, and batch operations each target different actions. However, move_mail, trash_mail, set_read_state individually overlap conceptually with their batch counterparts, and preview_send/send_mail plus preview_batch_actions/execute_batch_actions form pairs that could cause mis-selection if an agent isn't careful about which stage is needed.

    Naming Consistency4/5

    Tools follow a consistent verb_noun pattern (list_folders, read_mail, send_mail, trash_mail, move_mail, download_attachments, set_read_state, mail_status). A minor deviation exists with search_mail_headers and the pair preview_batch_actions/execute_batch_actions, which use a descriptive phrase style rather than a single verb, but the overall naming is coherent and predictable.

    Tool Count4/5

    At 12 tools, the count is reasonable for a mail MCP server covering read, search, send, move, trash, mark, attachment, batch, and status operations. It sits slightly above the ideal core set but each tool serves a distinct function; a couple of tools could theoretically be merged (e.g., single-action operations could be covered by batch), but the count is well within acceptable bounds.

    Completeness4/5

    The surface covers core mailbox operations: listing folders, status, searching, reading, sending, moving, trashing, marking read state, batch operations, and attachments. Minor gaps include no explicit compose/save-draft tool (preview_send acts as a proxy), no message-level threading/folder management (create/delete folders), and no way to fetch full content beyond a single message, but the main workflows are covered without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues