Skip to main content
Glama
Jorisslagter

maillog-mcp

by Jorisslagter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to maillog-mcp

No user-submitted related servers found.

    Related Servers

    • maillog-mcp by maillog-dev

      maillog-mcpofficial

      maillog-dev
      A
      license
      A
      quality
      C
      maintenance
      Enables an assistant to send email and list sent emails through the Maillog email API.
      2
      10 npm
      MIT

    • SMTP MCP Server

      samihalawa
      A
      license
      A
      quality
      A
      maintenance
      Enables sending emails via SMTP with template management, supporting multiple SMTP configurations, template creation with variable substitution, and bulk email sending with rate limiting.
      6
      150 npm
      21
      MIT

    • MCP Email Service

      Marary
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables sending emails (including mass emailing), querying, updating, and canceling delayed emails via the Resend API.
      -

    • Postmark MCP Server

      Lupiita4
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables sending and managing emails via Postmark, including email delivery with templates, template listing, and delivery statistics.
      MIT

    • sparkpost-mcp

      Pcummings
      A
      license
      B
      quality
      B
      maintenance
      Enables sending transactional emails, managing templates, suppression lists, sending domains, webhooks, subaccounts, and retrieving account metrics via the SparkPost API.
      20
      11 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

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    send_email and list_emails have clearly distinct purposes: one creates a new outgoing message, the other reads history of previously sent messages. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow the same verb_noun pattern (send_email, list_emails), making the set predictable and easy to navigate. The consistency is perfect for a two-tool surface.

    Tool Count3/5

    With only two tools, the server feels thin for a general email service, though the pair covers the two most essential actions. The count is borderline but not unreasonable for a narrowly scoped transactional email logging use case.

    Completeness4/5

    The core lifecycle of sending and verifying delivery is covered: create an email and list sent emails with status. A minor gap is the lack of a single-email detail endpoint or pagination control, but agents can likely work around that using list_emails.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources