Skip to main content
Glama
MailFlat

mailflat-mcp

Official

Related Servers

Alternatives to mailflat-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Disposable email MCP server for autonomous AI agents. Create labeled temporary inboxes, wait for verification emails, extract OTP codes and confirmation links — zero human intervention required.
      6
      20 PyPI
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that gives an AI agent a throwaway test identity — a real disposable email address and a real UK phone number — so it can sign up for something it's testing and read back the verification email/SMS itself, without a human in the loop.
      5
      223 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for disposable email — create inboxes, receive emails, and extract OTP codes. Let your AI agent sign up for services, wait for verification emails, and extract codes autonomously.
      7
      40 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Open-source, self-hosted Inbox-as-a-Service API for AI agents. It enables agents to manage email inboxes, send/receive emails, search messages, and wait for replies via REST or MCP.
      29
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for disposable email. Gives an assistant its own throwaway inbox, then hands back the confirmation code out of the message that arrives.
      5
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides AI agents with a persistent, agent-native email mailbox for sending, receiving, and managing emails through bounded-context retrieval, idempotent operations, and explicit acknowledgement.
      MIT

    TDQS

    A3.9/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: inbox lifecycle, message lifecycle, sending/waiting, and calendar event lifecycle are cleanly separated. The only close pair, send_email and reply, is explicitly differentiated in the descriptions.

    Naming Consistency4/5

    Almost all tools use consistent snake_case with an action_resource/entity pattern. A few names like reply and wait_until_sent are verb-only phrases, but they remain readable and snake_case throughout.

    Tool Count4/5

    19 tools is slightly heavy for the typical 3-15 sweet spot, but the server spans two domains (email inbox and calendar) so most tools are justified. No tool appears obviously redundant.

    Completeness4/5

    The surface covers most email inbox and calendar workflows: create/list/delete inboxes, read/mark/delete messages, send/reply/wait, and calendar create/list/update/cancel/rsvp/feed. Minor gaps exist, such as no explicit message update and attachment sending being delegated to the SDK.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues