Skip to main content
Glama
mailpal-com

mailpal-mcp

Official
by mailpal-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mailpal-mcp

No user-submitted related servers found.

    Related Servers

    • mailpal-mcp-server by mailpal-com

      mailpal-mcp-serverofficial

      mailpal-com
      A
      license
      Not graded
      quality
      D
      maintenance
      Free email server for AI agents with hardware attestation, enabling agents to send, receive, and manage emails via MCP tools.
      26 npm
      Apache 2.0

    • voidmail

      voidly-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Email for AI agents. Create inboxes, send and receive emails without phone or CAPTCHA.
      693 npm
      MIT
    • AgenticMail by agenticmail

      AgenticMailofficial

      agenticmail
      A
      license
      A
      quality
      A
      maintenance
      Real email and SMS for AI agents. Run a local mail server with disposable inboxes — agents send and receive real email, fetch verification codes, and drive a real inbox without going through any third-party email API.
      100
      225
      MIT
    • Lettio MCP by lettio-eu

      Lettio MCPofficial

      lettio-eu
      A
      license
      A
      quality
      B
      maintenance
      Private, EU-hosted email for AI agents over the open JMAP standard. Read, search, reply in-thread, organize and send from your own mailbox; sending is pinned to the signed-in mailbox.
      10
      108 npm
      MIT

    • 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
      -
    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.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one handles email, the other handles identity. There is no overlap or ambiguity between them.

    Naming Consistency2/5

    Both tool names are single-word product names, lacking any verb_noun pattern. They are not descriptive of actions, and there is no consistent naming convention for operations since all actions are hidden behind a generic 'operation' parameter.

    Tool Count2/5

    Only two tools for two domains (email and identity) is extremely thin. Each tool is a catch-all that requires further parameterization, making the count misleadingly low for the apparent scope.

    Completeness2/5

    The tools do not expose direct operations; they only serve as entry points to a readme. The actual functionality is not represented in the tool surface, leading to significant gaps for agents that cannot dynamically introspect.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources