AUTOMATIONSWITCH

Resend MCP

by Resend

Official Resend MCP for transactional and marketing email. Send, list, get, cancel, batch-send emails; manage contacts, audiences, broadcasts, domains, segments, topics, API keys, and webhooks. 506 GitHub stars and 22 commits on main in the last 30 days.

506·9 tools·Released SEP 2025·MIT
npx -y resend-mcp
Share:

Official Resend MCP for transactional and marketing email. Send, list, get, cancel, batch-send emails; manage contacts, audiences, broadcasts, domains, segments, topics, API keys, and webhooks. 506 GitHub stars and 22 commits on main in the last 30 days. MIT licence.

Reviewed by M. Nouriel · MAY 2026

INSTALL THIS SERVER

Requires authenticationRESEND_API_KEY environment variable for stdio mode; Bearer token from client for HTTP mode. Token from https://resend.com/api-keys.
{ "mcpServers": { "resend": { "command": "npx", "args": [ "-y", "resend-mcp" ], "env": { "RESEND_API_KEY": "<your-resend-key>" } } } }
PrereqRequires RESEND_API_KEY from https://resend.com/api-keys. Sending domains must be verified in Resend. NPM: `resend-mcp`. HTTP mode: `npx -y resend-mcp --http --port 3000` with Bearer token auth. Path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS).
{ "mcpServers": { "resend": { "command": "npx", "args": [ "-y", "resend-mcp" ], "env": { "RESEND_API_KEY": "<your-resend-key>" } } } }
{ "mcpServers": { "resend": { "command": "npx", "args": [ "-y", "resend-mcp" ], "env": { "RESEND_API_KEY": "<your-resend-key>" } } } }
{ "mcpServers": { "resend": { "command": "npx", "args": [ "-y", "resend-mcp" ], "env": { "RESEND_API_KEY": "<your-resend-key>" } } } }
{ "mcpServers": { "resend": { "command": "npx", "args": [ "-y", "resend-mcp" ], "env": { "RESEND_API_KEY": "<your-resend-key>" } } } }

9 TOOLS AVAILABLE

send_email
Send an email with HTML, plain text, attachments, CC/BCC, scheduling
Write
list_emails
List sent emails with filters
Read
get_email
Get a specific sent email
Read
batch_send_emails
Send multiple emails in one call
Write
list_audiences
List contact audiences
Read
list_contacts
List contacts in an audience
Read

OUR ASSESSMENT

Strengths
  • Official Resend maintenance.
  • 506 GitHub stars and MIT licence.
  • 22 commits on main in the last 30 days.
  • Two transports: stdio (default) and HTTP with Bearer token auth.
  • Resend API coverage spans emails, contacts, audiences, broadcasts, domains, segments, topics, API keys, webhooks.
  • HTTP mode passes RESEND_API_KEY via Bearer token, keeping the secret out of the URL.
  • Default sender and reply-to addresses configurable at startup via --sender and --reply-to flags.
  • Inbound email support: list and read received emails plus attachments.
Weaknesses
  • RESEND_API_KEY grants full Resend account access; scope tokens via Resend dashboard if available.
  • Sending domains must be verified in Resend before the MCP can send from them.
  • HTTP mode requires the operator to deploy the MCP on a network the agent can reach.
Security Notes

RESEND_API_KEY can send email from any verified sender domain on the Resend account. Scope the API key to a dedicated agent-only Resend project or workspace. For HTTP mode, the Bearer token mechanism keeps the key out of URLs and command lines; the deployment surface (the HTTP server) requires network-scoping to the agent host.

Best For

Teams using Resend for transactional or marketing email who want agents to send, list, or manage email campaigns; workflows where the agent triggers transactional emails as part of a longer task; operators who want a programmatic surface for Resend audiences and broadcasts.

TECHNICAL DETAILS

Language
typescript
Transport
stdiostreamable-http
Clients
Claude DesktopClaude CodeCursorVS CodeWindsurf
License
MIT
GitHub
npm
resend-mcp
Last Release
resend-mcp (npm latest)MAY 3, 2026
First Released
SEP 1, 2025

ADOPTION METRICS

// GitHub Stars
506

// Reading this506 stars on the resend/resend-mcp repo. 22 commits on main in the last 30 days. Official Resend maintenance carries the editorial weight.

// Popularity Rank
#1
Globally · #1 in API Integration

// Reading thisFirst-ranked in api expansion on official-vendor signal and tool-surface breadth.

SOURCES & VERIFICATION

We don't take any single directory's word for it. Before scoring, we cross-reference 5 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.

01
Discovered
Manual submission
First indexed MAY 3, 2026
02
Cross-referenced
5 directories
PulseMCP, MCP.so, Glama, Smithery, Official MCP Registry
03
Verified against
Claude Desktop, Claude Code, Cursor, VS Code
Installed and tested across clients
04
Last re-checked
MAY 3, 2026
Weekly re-verification
// How other directories see it

The same server, 5 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.

SourceTheir ratingTheir star countTheir downloadsLast synced
AutomationSwitch This page4.4editorial506MAY 3, 2026
PulseMCP— unratedunavailableunavailableMAY 3, 2026
MCP.so— unratedunavailableunavailableMAY 3, 2026
Glama— unratedunavailableunavailableMAY 3, 2026
Smithery— unratedunavailableunavailableMAY 3, 2026
Official MCP Registry— unratedunavailableunavailableMAY 3, 2026

// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.

// Get in touch

DISCUSS YOUR
MCP REQUIREMENTS.

Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.

Discuss Your MCP Requirements →