Resend is a Communication MCP server that lets Claude Code, Cursor, Windsurf and any MCP-compatible AI agent send and track transactional emails via the Resend API from any MCP-compatible agent. Install in 1 minute with mcpizy install resend.
Communication
Send and track transactional emails via the Resend API from any MCP-compatible agent.
Connect your Resend account once — MCPizy stores the credentials encrypted and uses them whenever you run a recipe in managed mode.
mcpizy install resendnpx -y @resend/mcp-serversend_emailSend a transactional email
Inputs
fromstringrequiredtostring[]requiredsubjectstringrequiredhtmlstringoptionaltextstringoptionallist_emailsList recent sent emails
get_emailGet the status of a sent email by ID
Inputs
email_idstringrequiredlist_domainsList verified sender domains
add_domainRegister a new sender domain
Inputs
namestringrequiredWorks identically across clients. Only the config file path differs.
~/.claude.json{
"mcpServers": {
"resend": {
"command": "npx",
"args": [
"-y",
"@resend/mcp-send-email"
],
"env": {
"RESEND_API_KEY": "re_..."
}
}
}
}.cursor/mcp.json{
"mcpServers": {
"resend": {
"command": "npx",
"args": [
"-y",
"@resend/mcp-send-email"
],
"env": {
"RESEND_API_KEY": "re_..."
}
}
}
}~/.codeium/windsurf/mcp_config.json{
"mcpServers": {
"resend": {
"command": "npx",
"args": [
"-y",
"@resend/mcp-send-email"
],
"env": {
"RESEND_API_KEY": "re_..."
}
}
}
}Create an API key in the Resend dashboard
RESEND_API_KEYVerify your sender domain (add DNS records)
Paste any of these prompts into Claude Code, Cursor or another MCP-compatible client.
“Send an email to [email protected] with subject 'Weekly report' and my draft body”
Uses: send_email
“Did my latest marketing email bounce?”
Uses: list_emails, get_email
“Which domains do I have verified for sending?”
Uses: list_domains
Resend MCP wraps the Resend API (api.resend.com), a modern developer-first transactional email service. Primitives are Emails (single send or batch), Domains, API Keys, Audiences, Contacts, and Broadcasts (marketing emails). Auth uses Bearer API keys. Tools include emails_send (with React/HTML/text), emails_send_batch (up to 100 emails per call), domains_verify, contacts_create, broadcasts_create, and broadcasts_send. The killer feature is first-class support for React Email components — you can pass React JSX as the email body and Resend renders it server-side.
We use Resend for product transactional email in modern stacks (Next.js, Remix, SvelteKit) where the team wants to author emails as React components instead of HTML strings or Handlebars templates. Common workflows: signup confirmation, password reset, magic links, weekly digest broadcasts, and team invite emails. Token cost is minimal (100-300 tokens per send). Pricing is competitive: free tier gives 3k emails/month and 100 emails/day, paid starts at $20/month for 50k emails. Domain verification uses standard SPF/DKIM/DMARC.
Vs. SendGrid, Resend has a dramatically cleaner API and SDK but a smaller feature surface — no advanced segmentation, no journey builder, fewer analytics. Vs. Postmark, Resend is younger and has less deliverability history but a more developer-friendly UX. Trade-offs: marketing features (Broadcasts, Audiences) are newer and less mature than SendGrid's; webhook event coverage is good but less granular than competitors; analytics dashboards are minimal.
React Email rendering happens server-side on Resend's infrastructure — if your component imports anything beyond @react-email/components, the render will fail with cryptic errors. Test locally with react-email preview first.
Domain verification can take up to 72 hours for DNS propagation, but Resend's UI says "verified" the moment all records are detected — sometimes the actual mail flow takes another 1-2 hours due to upstream caching.
The batch send endpoint accepts up to 100 emails per call, but if any one email has an invalid recipient, the entire batch fails with no partial success. Validate emails before batching.
Free tier allows only 100 emails per day even within the 3k/month allowance — bursty sends will hit daily limit before monthly limit.
Honest pros/cons against the closest communication MCP servers.
| Server | Strengths | Trade-offs |
|---|---|---|
| SendGrid MCP | Mature deliverability, deep feature set, marketing campaigns built in, more event types | Older API design, less developer-friendly, no native React Email support |
| Postmark MCP | Best-in-class transactional reputation, separate streams for transactional vs marketing, fastest median delivery time | Pricier, no native marketing automation, smaller ecosystem of templates |
| Loops.so | Marketing-focused, great for SaaS onboarding sequences, no-code email builder | Less suited to pure transactional, smaller API surface, newer product |
If Resend doesn't fit your stack, these Communication MCP servers solve similar problems.
The Resend MCP server is an Communication Model Context Protocol server that lets Claude Code, Cursor, Windsurf, VS Code with Copilot, and other MCP-compatible AI agents send and track transactional emails via the Resend API from any MCP-compatible agent. It exposes Resend's capabilities as tools the AI can call directly from your editor or CLI.
The fastest way is the MCPizy CLI: run `mcpizy install resend` and MCPizy will add the server to your `.claude.json` automatically. You can also install it manually by adding an entry under `mcpServers` in `.claude.json` with the command `npx -y @resend/mcp-server` and restarting Claude Code.
Yes. The Resend MCP server is free and open source (see the GitHub repository linked on this page). You may still need a Resend account or API key to connect the server to the underlying service, but the MCP layer itself has no MCPizy subscription cost.
Yes. Any MCP-compatible client works — including Claude Code, Claude Desktop, Cursor (via `.cursor/mcp.json`), Windsurf, VS Code with Copilot Chat, and custom agents built on the MCP SDK. The same install command targets all of them; only the config file path differs.
Once installed, your AI agent can send and track transactional emails via the Resend API from any MCP-compatible agent directly inside your conversation. Typical use cases include asking Claude Code or Cursor to run Resend operations, inspect results, chain Resend with other MCP servers (see our Workflow Recipes), and automate repetitive communication tasks without leaving your editor.