Skip to main content
Glama
Sign In
MepMail

MepMail

by JE4NVRG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MepMail

No user-submitted related servers found.

    Related Servers

    • Wraps Email for Amazon SES

      wraps-team
      A
      license
      A
      quality
      B
      maintenance
      Send email through your own Amazon SES account, and check domain verification, the suppression list and sandbox status. Works with any SES account; Wraps adds send history and delivery events.
      7
      1
      MIT
    • Sendmux Email Inbox API + Sending

      Sendmux Email Inbox API +official

      qubrics
      A
      license
      B
      quality
      A
      maintenance
      Sendmux is an email inbox API and email API for AI agents. Use this MCP server to let authorised agents work with Sendmux mailboxes, inbound email, clean JSON parsing, webhooks, outbound sending, provider routing, logs, billing, and team controls.
      104
      58
      MIT

    • multi-mail-mcp

      claygeo
      F
      license
      A
      quality
      C
      maintenance
      Local-first MCP server for agents that need to work across multiple Gmail and Microsoft 365 accounts without cloud token storage.
      6
      -

    • gmail-agent MCP server

      dremok
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search, read, send, reply, forward and draft mail, download and extract attachments, and manage labels, stars, archive and trash. It runs over stdio and talks straight to the Gmail API with the user's own OAuth credentials, so no third-party server sits in between.
      43 PyPI
      1
      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

    A3.6/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools are clearly distinct, especially with the mailbox_ prefix separating the inbox surface from the transactional email API. The main overlap is between transactional email tools (list_emails/get_email) and mailbox message tools (mailbox_list_messages/mailbox_read_message), plus broadcasts vs emails, but descriptions clarify the boundaries.

    Naming Consistency5/5

    All tool names use consistent snake_case verb_noun form, with mailbox_ as a clear namespace prefix. Minor verb choice like mailbox_read_message instead of get is still within the same pattern.

    Tool Count2/5

    28 tools is heavy and exceeds the well-scoped range. While two surfaces (transactional API and mailbox) justify many tools, the set includes numerous read-only list/get pairs that weigh it down, and several resources lack write operations.

    Completeness3/5

    Contacts have full CRUD and core sending/reading workflows are covered. However, templates, broadcasts, domains, webhooks and suppressions are list/get-only, and the mailbox surface lacks delete, move or mark operations, leaving notable lifecycle gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources