Skip to main content
Glama
ni-c

smtp-mcp

by ni-c
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to smtp-mcp

No user-submitted related servers found.

    Related Servers

    • MailPace MCP Server by mailpace

      MailPace MCP Serverofficial

      mailpace
      A
      license
      D
      quality
      D
      maintenance
      An MCP server implementation that allows sending emails over MailPace's fast transactional email API.
      1
      1
      MIT

    • tvram-backend-mcp

      amoghar29
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes an email verification tool, returning verdicts of valid, invalid, or risky with reasons.
      -

    • email-mcp

      yashjoshiatgit
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server that empowers AI agents to securely send emails via SMTP, supporting plain text, HTML, and attachments.
      MIT

    • communication-mcp-server

      ajaysingh16601
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides email communication tools (send email, health check, list providers) via SMTP, accessible over HTTP/SSE for remote AI clients like Claude Desktop.
      8 npm
      MIT
    • fagents-mcp by fagents

      fagents-mcpofficial

      fagents
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables Claude Code agents to send and read emails via SMTP/IMAP with per-agent credential isolation and audit logging.
      MIT

    • smtp-mcp-wrapper

      JB09
      F
      license
      Not graded
      quality
      B
      maintenance
      A minimal MCP server that provides a send_email tool for sending HTML email through an SMTP relay.
      -
    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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: test_connection verifies connectivity, get_server_info provides configuration details, preview_mail builds a message without sending, and validate_recipients checks recipient permissions. There is no overlap or ambiguity between these tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (test_connection, get_server_info, preview_mail, validate_recipients). This uniformity makes the toolset predictable and easy to navigate.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose of SMTP configuration verification and pre-send checks. Each tool addresses a distinct aspect of the workflow, and the count is neither too sparse nor excessive for the stated functionality.

    Completeness5/5

    The toolset fully covers the domain of pre-send validation: retrieving server info, testing the connection, previewing messages with all checks, and validating recipients. The absence of a send tool is intentional (conditional on SMTP_ALLOW_SEND), so the surface is complete for its defined scope.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources