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.
      25 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.
      50
      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
      34 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
      12 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 106 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource and action, and many descriptions explicitly disambiguate with 'NOT for' guidance. A few multi-action tools such as get-automation and manage-events blur list/get/create/update boundaries, but the overall surface is largely separable.

    Naming Consistency5/5

    Tool names consistently use kebab-case with predictable verb-noun phrasing such as list-emails, create-broadcast, and remove-contact. Minor deviations like manage-events and batch-add-suppressions still fit the broader naming convention.

    Tool Count1/5

    106 tools is an extreme mismatch for a practical MCP surface, far exceeding the 50+ threshold for severe over-scoping. While the underlying Resend API is broad, this should be consolidated or split rather than exposed as one massive toolset.

    Completeness5/5

    The toolset covers nearly the entire Resend lifecycle: sending, received emails, broadcasts, templates, contacts, segments, domains, webhooks, automations, events, suppressions, logs, OAuth, API keys, and metrics. CRUD and operational coverage are present for almost every resource, with very few obvious gaps.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources