Skip to main content
Glama
Fluma-Intelligence

Cloud Mail MCP

Related Servers

Alternatives to Cloud Mail MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables a locally-running agent to read and organize email from Gmail, Microsoft 365, and IMAP mailboxes with restricted, audited access.
      GPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to multiple email accounts, including Gmail via App Password and generic IMAP providers, so an agent can list accounts and folders, search messages, and fetch messages or attachments. All operations are strictly read-only, with no sending, writing, deleting, or moving.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only email access over a remote HTTP MCP endpoint, enabling agents to search mailboxes, read messages, and retrieve attachments from self-hosted IMAP accounts with OAuth-authenticated access.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables controlled Microsoft 365 mail workflows including search, read, thread, attachment, and managed draft operations through Microsoft Graph, without sending or modifying messages.
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, read, organize, draft, send, and schedule email through a scoped token, with actions journaled and reversible. It also supports proposal queues, approval workflows, and undo operations for safe mailbox automation.
      0
      8
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to read, search, organise, and manage IMAP mailbox messages, including saving attachments and drafting replies, while treating mail content as untrusted and keeping write capabilities opt-in.
      6
      208 npm
      3
      MIT

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: list vs get vs search for messages, metadata vs content for attachments, and complete CRUD separation for drafts. Minor overlaps (list_messages/search_messages, list_mailboxes/mail_status) are clearly differentiated by their descriptions.

    Naming Consistency4/5

    Almost all tools follow a predictable snake_case verb_noun pattern (list_, get_, create_, update_, delete_, download_). The noun-first 'mail_status' is an outlier and is slightly inconsistent with 'get_send_status', but the overall convention is strong.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range for a mail server covering mailboxes, messages, attachments, drafts, and status. Each tool appears to earn its place with no obvious redundancy.

    Completeness2/5

    The surface lacks any send operation despite offering get_send_status for send receipts, and message management (delete, move, mark read/unread) is entirely absent. Attachment upload and draft sending are also missing, leaving significant gaps for a cloud mail server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues