MCP Server

Email & CommunicationDeveloper APIAPI Key Required

Resend MCP Server

by Community · Model Context Protocol for Resend

Resend MCP Server gives your AI coding assistant the ability to send transactional emails directly from agent workflows. Using the Resend API — the developer-first email platform built for modern applications — agents can send HTML emails, use React Email templates, manage contact lists, and retrieve delivery logs through structured MCP tool calls.

Whether you're building an onboarding agent that welcomes new users, a monitoring agent that alerts your team when something breaks, or a reporting agent that delivers weekly digests, Resend MCP makes email delivery a first-class capability in your Claude Code workflows. The free tier covers 100 emails per day — more than enough to get started.

100 free

Emails/day

on Resend free tier

Supported

Templates

React Email components

API Key

Auth

per-domain scoping

React/Node

SDKs

React Email compatible

Quick Install

claude mcp add resend -- npx resend-mcp

Key Features

Transactional Email Sending

Send individual HTML or plain-text emails with full control over from, to, subject, reply-to, CC, BCC, and custom headers. Agents can compose email content dynamically and dispatch it in a single MCP call. Supports both immediate sending and scheduled delivery for time-sensitive notifications.

React Email Template Support

Use pre-built React Email component templates for consistent, branded email design. Pass structured data to templates to render personalized content — recipient name, account details, order information, usage statistics — without the agent generating raw HTML. Templates are version-controlled and maintainable by your engineering team.

Delivery Status Tracking

Retrieve email delivery logs and status for sent messages. Check whether an email was delivered, opened, bounced, or marked as spam. Agents can use delivery status as a signal in workflows — retry a notification if an email bounced, or follow up through a different channel if an important message was not delivered.

Contact & Audience Management

Create, update, and delete contacts within Resend audiences. List contacts, retrieve individual contact details, and manage subscription status. This enables agents to maintain clean contact lists — adding new users on signup, updating preferences on profile changes, and removing contacts on unsubscribe or account deletion.

Domain-Scoped API Keys

Resend supports creating API keys scoped to specific sending domains. This lets you create separate keys for your marketing domain (newsletter.yourdomain.com) and transactional domain (notifications.yourdomain.com), giving different agents or services the minimum permissions needed for their specific email sending role.

Developer-First Reliability

Resend is built specifically for developers sending transactional email, with high deliverability rates, automatic DKIM/SPF configuration, suppression list management, and webhook support for delivery events. Agents inherit all of Resend's deliverability infrastructure without managing any of the underlying email server complexity.

Execution Brief

Use this page as a rollout checklist, not just reference text.

Suggest update

Tool Mapping Lens

Organize Tools by Workflow Phase

Catalog-oriented pages work best when users can map discovery, evaluation, and rollout in a clear path instead of reading an undifferentiated list.

Define the job-to-be-done first
Group tools by stage
Prioritize by adoption friction

Actionable Utility Module

Skill Implementation Board

Use this board for Resend MCP Server before rollout. Capture inputs, apply one decision rule, execute the checklist, and log outcome.

Input: Objective

Deliver one measurable improvement with resend mcp server claude code transactional email react email template agent workflow

Input: Baseline Window

20-30 minutes

Input: Fallback Window

8-12 minutes

Decision Trigger	Action	Expected Output
Input: one workflow objective and release owner are defined	Run preview execution with fixed acceptance criteria.	Go or hold decision backed by repeatable evidence.
Input: output quality below baseline or retries increase	Limit scope, isolate root issue, and rerun controlled test.	One confirmed correction path before wider rollout.
Input: checks pass for two consecutive replay windows	Promote to broader traffic with fallback path active.	Stable rollout with low operational surprise.

Execution Steps

Record objective, owner, and stop condition.
Execute one controlled preview run.
Measure quality, latency, and correction burden.
Promote only when pass criteria are stable.

Output Template

tool=resend mcp server claude code transactional email react email template agent workflow
objective=
preview_result=pass|fail
primary_metric=
next_step=rollout|patch|hold

Share execution feedback

What Is Resend MCP Server?

Resend MCP Server is a Model Context Protocol integration that enables AI coding assistants to send transactional emails and manage contact lists through the Resend API. It exposes email sending, delivery tracking, and audience management as structured MCP tools that Claude Code or any compatible client can call during agent workflows.

Resend is a developer-first email API built for modern applications, offering high deliverability, React Email template support, and clean developer ergonomics. Unlike legacy SMTP services or complex email platforms, Resend is designed for programmatic use — which makes it a natural fit for AI agents that need to send emails as part of larger workflows.

Authentication is straightforward: a single API key set as RESEND_API_KEY gives agents access to all sending and management capabilities for your verified domains. Keys can be scoped per domain to enforce separation between transactional and marketing email streams. Resend handles all the deliverability infrastructure — DKIM signing, SPF validation, bounce handling, and suppression lists — so agents can focus on when and what to send rather than how to deliver it.

Resend MCP pairs naturally with other data-access MCP servers. An agent can query new user signups from Supabase MCP, then use Resend MCP to send each new user a personalized welcome email. A monitoring agent can detect anomalies using Postgres MCP queries, then immediately dispatch alert emails to the responsible team members. Email becomes a natural output channel in any agent workflow that needs to communicate with humans.

How to Calculate Better Results with resend mcp server claude code transactional email react email template agent workflow

Create a Resend account at resend.com and verify your sending domain by adding the required DNS records. Generate an API key from your Resend dashboard and set it as RESEND_API_KEY in your environment. If you are testing without a custom domain, Resend provides a sandbox sending address for development use.

Install the Resend MCP server using the npx command and register it with your AI client. The server connects to the Resend API immediately — no additional configuration is required beyond the API key.

Start by sending a test email to yourself to verify the connection and confirm your sending domain is working correctly. Check the Resend dashboard to see delivery status and ensure emails are arriving as expected before integrating email sending into larger agent workflows.

For production workflows, create React Email templates for your most common email types and commit them to your repository. Reference templates by name in your agent prompts so the agent sends branded, well-formatted emails rather than generating raw HTML at runtime. This approach keeps email design in version control and gives your team full control over email appearance.

Treat this page as a decision map. Build a shortlist fast, then run a focused second pass for security, ownership, and operational fit.

When a team keeps one shared selection rubric, tool adoption speeds up because evaluators stop debating criteria every time a new option appears.

Worked Examples

Automated new user onboarding email sequence

A new user signs up and their account data is available in the agent's context (name, email, plan, signup source)
The agent queries Supabase MCP to retrieve the user's account details and the features available on their plan
The agent uses Resend MCP to send a personalized welcome email using the welcome-email React Email template, passing in the user's name and plan-specific feature highlights
The agent adds the new user to the appropriate Resend audience segment based on their plan tier (free-tier or paid-tier audience)
The agent sends a second email 30 minutes later (or schedules it) with a getting-started guide tailored to their use case based on signup survey responses
A delivery status check verifies the welcome email was delivered; if it bounced, the agent logs the bounce and flags the account for manual review

Outcome: A complete onboarding email sequence that sends personalized, templated emails based on user context — delivered reliably and tracked, with bounce handling to catch bad email addresses at signup.

Weekly analytics digest email for team stakeholders

Every Monday morning, an agent is triggered to compile the weekly metrics digest
The agent queries Postgres MCP to retrieve the previous week's key metrics: new signups, active users, revenue, top-performing content
The agent formats the data into a structured object matching the weekly-digest React Email template's expected props
The agent retrieves the stakeholder email list from the Resend audience management tool to get the current list of digest subscribers
Resend MCP sends the formatted digest to all subscribers using the weekly-digest template, with each email personalized with the recipient's name
The agent logs the send event with recipient count and delivery statistics for audit purposes

Outcome: A fully automated weekly email digest that pulls live data, formats it into a branded template, and delivers it to all stakeholders — with no manual compilation or sending required.

Frequently Asked Questions

What is the Resend MCP Server?

Resend MCP Server is a Model Context Protocol integration that gives AI coding assistants the ability to send transactional emails and manage email contacts through the Resend API. It exposes Resend's send, list, contact, and audience management operations as MCP tools that Claude Code or any compatible client can call. This enables agent workflows that include email delivery — welcome emails, notifications, reports, confirmations — without the agent needing to manage SMTP configuration or complex email service SDKs directly.

What email operations does Resend MCP support?

Resend MCP supports the core operations of the Resend API: sending individual emails with HTML or text content, sending emails using pre-built templates, retrieving email delivery status and logs, managing contacts within audiences (create, update, delete, list), and managing audience lists. For developer-focused workflows, it also supports sending emails rendered from React Email components when the server is configured with your template library. This covers the full lifecycle from sending to delivery tracking to list management.

How do I authenticate with Resend MCP?

Authentication uses a Resend API key generated from your Resend dashboard at resend.com. Set the key as the RESEND_API_KEY environment variable before starting the MCP server. Resend API keys are scoped to a domain — you can create separate keys for different sending domains or environments (production versus staging). Use a restricted key with only the permissions your agent needs: sending-only keys for agents that only dispatch emails, and full-access keys only when contact or audience management is also required.

Can agents use React Email templates with Resend MCP?

Yes, when the Resend MCP server is configured with your React Email template library, agents can reference templates by name and pass variable data to render personalized emails. React Email is Resend's open-source component library for building email templates using React syntax. Templates can include dynamic content (recipient name, order details, account information) that the agent populates at send time. This allows agents to send well-designed, consistently branded emails without generating raw HTML themselves.

What is the free tier limit for Resend?

Resend's free tier allows up to 100 emails per day and 3000 emails per month with one sending domain. This is generous enough for development workflows, testing, and low-volume production use cases. For production agent workflows sending higher volumes — onboarding sequences, weekly reports, notification systems — Resend's paid plans start at competitive rates with higher daily and monthly limits, dedicated IP options, and advanced delivery analytics. Check resend.com/pricing for current plan details.

What are common use cases for Resend MCP in agent workflows?

Common use cases include: new user onboarding agents that send personalized welcome emails with account setup instructions, monitoring agents that email alerts when anomalies are detected in data or system metrics, report generation agents that compile weekly summaries and email them to stakeholders, lead nurturing agents that send follow-up emails based on contact behavior, e-commerce agents that send order confirmation and shipping notification emails, and scheduled digest agents that aggregate important updates and deliver them as daily or weekly email briefings.

Missing a better tool match?

Send the exact workflow you are solving and we will prioritize a new comparison or rollout guide.

Submit feedback