Skip to main content
Glama
ElizioMartins

mcp-emailjs

by ElizioMartins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-emailjs

No user-submitted related servers found.

    Related Servers

    • mcp-email-sender

      AMEOBIUS-space
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to validate email addresses and send emails via SMTP with zero external dependencies.
      MIT

    • 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

    • email-mcp-server

      egyptianego17
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to send emails via SMTP, supporting simple and custom emails with attachments and CC/BCC, plus connection testing.
      3
      28
      MIT

    • OutreachEmailMCP

      BreazyLabs
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that acts as an email gateway for Gmail and Microsoft 365, enabling AI agents to send and read emails via MCP tools, with SMTP/IMAP and REST APIs for email sequencing and automation.
      1
      AGPL 3.0

    • Shoot Email

      powersurge01
      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
    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.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: retrieving history, sending emails, and validating configuration. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (get_email_history, send_email, validate_config).

    Tool Count5/5

    Three tools is well-scoped for an email service, covering the core operations without unnecessary bloat.

    Completeness4/5

    The set covers sending, history, and config validation. Minor gap: lacks template management or cancellation, but core workflow is complete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources