Skip to main content
Glama
resend

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Email Sending MCP

No user-submitted related servers found.

    Related Servers

    • Email sending MCP

      deploya-labs
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that allows Claude Desktop or Cursor to send emails directly using Resend's API, eliminating the need to copy-paste email content.
      5 npm
      MIT

    • protonmail-mcp

      amotivv
      A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server provides email sending functionality using Protonmail's SMTP service. It allows both Claude Desktop and Cline VSCode extension to send emails on your behalf using your Protonmail credentials.
      49
      MIT

    • 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.
      -

    • Resend MCP Server

      friendlygeorge
      A
      license
      A
      quality
      F
      maintenance
      An MCP server for the Resend email API, enabling AI assistants to send emails, manage contacts, audiences, and domains through natural language.
      18
      23 npm
      MIT

    • email

      eleanorreem
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables Claude Desktop to manage emails via SMTP and IMAP. Send emails, fetch unread messages, and create draft replies directly from conversations.
      3
      13 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

    A3.7/5.0

    Scored across 105 tools

    Disambiguation5/5

    Every tool targets a distinct resource or action, and descriptions explicitly say what each is NOT for (e.g., send-email vs send-broadcast vs send-batch-emails), leaving no ambiguity. Even closely related compose/update/content tools are clearly separated with workflow guidance.

    Naming Consistency4/5

    Overall the hyphenated verb_noun pattern is consistent (create-, list-, get-, update-, remove-, send-, compose-). Minor deviations exist—compound verbs like rotate-webhook-signing-secret, batch-add-suppressions, and manage-events—but they are still readable and predictable.

    Tool Count1/5

    105 tools is extreme over-fragmentation for an email server facilitation surface. Many could be consolidated or paramterized (as manage-events already demonstrates), and the sheer volume will overwhelm agents with selection and reasoning overhead.

    Completeness5/5

    The tool set thoroughly covers the Resend domain: transactional email, broadcasts, templates, contacts/segments/topics/suppressions/imports, domains, webhooks with replay and attempts, automations, logs, API keys, OAuth grants, and metrics. There are no obvious missing lifecycle operations or dead ends.

    Maintenance

    ActivityNo data
    ResponsivenessSlow

    Resources