Skip to main content
Glama

Related Servers

Alternatives to 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
      Not graded
      quality
      D
      maintenance
      Multi-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.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Cross-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 npm
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A 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.
      6
      1
      -
    • 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
      Not graded
      quality
      B
      maintenance
      Local MCP server for personal Outlook.com/Hotmail/Live accounts, enabling email triage, folder management, bulk operations, and newsletter unsubscribe via Microsoft Graph.
      -

    TDQS

    B3/5.0

    Scored across 31 tools

    Disambiguation2/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive