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.
      4 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
      21 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
      28 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.6/5.0

    Scored across 136 tools

    Disambiguation4/5

    Despite 136 tools, nearly every description carries explicit 'NOT for' cross-references that steer the agent away from near-neighbors (send-email vs send-batch-emails vs send-new-inbox-email; list-inbox-threads vs search-inbox-threads vs list-inbox-thread-emails; compose vs update variants). A few boundaries still blur—especially the create/send/duplicate/cancel broadcast cluster and the many overlapping list tools—but the set is unusually well-disambiguated for its size.

    Naming Consistency4/5

    Overwhelmingly consistent snake_case verb_noun (list-contacts, create-broadcast, remove-webhook, add-inbox-thread-labels). Minor deviations exist: compound multi-action tools like manage-events and dual-mode tools like get-automation/get-usage, plus connect-to-editor/disconnect-from-editor. Pattern is still highly predictable.

    Tool Count2/5

    136 tools is far past the heavy threshold, even for a platform as broad as Resend. While each tool maps to a distinct API endpoint and the domain is genuinely large, the sheer surface imposes heavy selection cost and context load on an agent. This is over-scoped for practical agent use.

    Completeness4/5

    Coverage is excellent—full CRUD across contacts, domains, broadcasts, templates, topics, segments, webhooks, API keys, inboxes, threads, labels, drafts, suppressions, automations, and events, plus logs, metrics, and usage. The main dead end is attachments: they can be listed but their contents cannot be downloaded through this server.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources