Skip to main content
Glama
AssistantMail

Assistant Mail

Official
by AssistantMail
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Assistant Mail

No user-submitted related servers found.

    Related Servers

    • AgentMail

      agentmail-to
      -
      license
      C
      quality
      C
      maintenance
      Gives on-the-fly inboxes to AI agents. Agents / LLM's can send, receive, and take action in isolated inboxes. Built for AI unlike Gmail. Check us out at agentmail.to
      10
      101
      -

    • lenovmail

      satuapps
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely read, search, and send email across IMAP and Microsoft Graph accounts, with scoped tokens, approval flows, and an audit trail.
      1
      MIT

    • MCP Emails

      Albretsen
      A
      license
      A
      quality
      A
      maintenance
      Hosted email MCP server for AI agents. Connect Gmail or any IMAP/SMTP mailbox (Fastmail, iCloud, Yahoo, Zoho, Yandex) to Claude, ChatGPT, Cursor and any MCP client to read, search, send, organize, schedule and auto-triage email. Mail is fetched live and never stored.
      23
      8
      AGPL 3.0

    • gigamail

      adecubed
      A
      license
      A
      quality
      A
      maintenance
      Your real mailbox and calendar for your AI agent — Microsoft 365 via Graph or any IMAP — as 24 tools: read, search, attachments as text, sender history, drafting from identity and knowledge files, free-slot computation. Send, reply, delete and calendar writes need out-of-band human approval: the agent cannot approve its own actions.
      29
      142 PyPI
      8
      AGPL 3.0

    • Postfleet MCP

      Thestral12
      A
      license
      A
      quality
      B
      maintenance
      Gives AI agents their own email address with inbound parsing, classification, extraction, and prompt injection screening, plus tools to manage mailboxes, send/receive emails, and handle draft approval workflows.
      14
      56 npm
      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

    C2.9/5.0

    Scored across 22 tools

    Disambiguation3/5

    Most tools map to distinct resources, but the four *_reference tools (get_message_reference, list_messages_reference, send_email_reference, get_usage_reference) closely parallel their non-reference counterparts and could be confused. get_me and health also overlap somewhat as account/server metadata lookups.

    Naming Consistency4/5

    Tool names consistently use the assistantmail_ prefix with snake_case verb_noun patterns. Minor deviations (health, *_reference suffix) break the pattern slightly but the convention remains predictable.

    Tool Count3/5

    22 tools is on the higher end and feels somewhat heavy. The core operations are justified, but the four reference-style tools inflate the count and could have been consolidated.

    Completeness4/5

    The server covers the main email lifecycle: mailbox CRUD, message listing/retrieval/send/reply/delete, recipient management, usage, and inbound policy. Minor gaps like message read-state updates or attachment handling are absent, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources