Skip to main content
Glama

Related Servers

Alternatives to gigamail

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read, search, send, and organize email over IMAP and SMTP for providers such as Gmail, Yahoo, iCloud, Zoho, Fastmail, and custom domains, with tools for attachments, drafts, templates, scheduling, and safe mailbox management.
      282 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, read, organize, and draft replies in any IMAP mailbox, with messages sent only after explicit approval. Supports multiple isolated mailboxes, OAuth-based access, and keeps no mail content in its database.
      36 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search and read email, inspect attachments, and optionally send messages and organize folders through existing IMAP and SMTP mailboxes. Supports Docker, stdio, and HTTPS OAuth deployment with read-only or full-access modes.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to manage mailbox contents and schedules through IMAP/SMTP/CalDAV, including searching, reading, sending emails with signatures and attachments, and creating or responding to calendar events.
      19
      MIT

    TDQS

    A4/5.0

    Scored across 31 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action, and the descriptions actively steer agents between near-neighbors (list_unread vs list_messages, find_free_slots vs list_events, move_message vs delete_message). The only genuinely confusable clusters are the three text-extraction tools (read_attachment, read_knowledge_file, drive_read_file) and the two drafting-context tools (sender_history, observer_context), which are separated mostly by source wording rather than by name.

    Naming Consistency4/5

    The dominant pattern is verb_noun (list_messages, read_message, send_mail, delete_folder, create_event), extended with a drive_ prefix for the Google Drive subset. The deviations are minor: three noun-only tools (sender_history, observer_context, memory_stats) and the mixed position of the drive_ prefix, but nothing is chaotic or camelCase.

    Tool Count3/5

    31 tools is heavy for an agent surface, but the server genuinely spans four domains (mail, calendar, Zoom, Drive) plus knowledge/memory context, and each integration has a minimal set. A few context/health tools (memory_stats, observer_context) feel auxiliary rather than essential at this count.

    Completeness4/5

    Mail lifecycle is close to complete: list/read/send/reply/draft/move/delete/mark-read, folder create+delete, search, attachments and guardrailed two-phase approvals. The remaining gaps are real but survivable: no event update/reschedule, no forward_mail, and Drive lacks move/share/search (accounts are deliberately read-only by design).

    Maintenance

    ActivityActive
    ResponsivenessLimited data