Skip to main content
Glama
friendlygeorge

Resend MCP Server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Resend MCP Server

No user-submitted related servers found.

    Related Servers

    • Resend MCP Server

      huazhengwang
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Multi-Agent Conversation Protocol) Server for interacting with Resend's email API, auto-generated using AG2's MCP builder to enable sending emails through natural language.
      -

    • PostStack MCP Server

      getpoststack
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for the PostStack email API that enables AI assistants to send transactional emails, manage contacts, handle inbound email threads, and perform deliverability checks through 84 curated tools.
      84
      24 npm
      1
      MIT

    • Gmail MCP Server

      Abhitkumar89
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI assistants send, read, and manage Gmail through natural language, including email sending, inbox management, and template-based outreach.
      132 npm
      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
    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.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action. Send_email vs send_batch_email are clearly differentiated by batch vs single. CRUD operations for each resource are separate and unambiguous.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase snake_case (e.g., create_api_key, list_domains). No mixing of styles or inconsistent verbs.

    Tool Count5/5

    18 tools cover the main resources of an email service (API keys, audiences, contacts, domains, emails) without being excessive. Each tool serves a clear purpose.

    Completeness5/5

    The tool surface provides full CRUD for API keys (create, list, delete), domains (create, list, delete, verify), audiences (create, list), contacts (create, list, get, update, delete), and emails (send, send_batch, get, list). No obvious gaps for typical email API operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources