Resend MCP Server
Official Resend MCP server: send and receive emails, manage domains, contacts, broadcasts, and automations – directly from your AI client.
- Skill Road
- Resend MCP Server
Categories
Description
The Resend MCP Server is the official Model Context Protocol server for the Resend email platform. It connects compatible AI clients — including Claude Code, Claude Desktop, Codex, Cursor, GitHub Copilot, Windsurf, Warp, and Devin — directly to the Resend API. Developers can manage email infrastructure in natural language: send emails, maintain contact lists, control broadcast campaigns, set up domains, and configure automations. The official documentation is at https://resend.com/docs/mcp-server; the open-source repository lives at https://github.com/resend/resend-mcp.
What is the Resend MCP Server?
According to the provider, Resend is an email API for developers that supports both transactional emails (registration confirmations, password resets, order notifications) and marketing emails (newsletters, broadcast campaigns). The MCP server extends this platform with a standardised interface for AI agents based on the Model Context Protocol (MCP). Resend offers two operating modes: a hosted remote server at https://mcp.resend.com/mcp (no local installation required, authentication via OAuth or an API key as a Bearer token) and a local server via npx resend-mcp (stdio or HTTP, API key as an environment variable). Both modes use the same open-source TypeScript code under the MIT licence.
Prerequisites
Using the Resend MCP Server requires: an active Resend account (free entry tier available), a compatible MCP client (Claude Code, Claude Desktop, Codex, Cursor, GitHub Copilot, Windsurf, Warp, Devin, or any MCP-compatible client), and a Resend API key or OAuth consent for authentication. To send from a custom domain, the domain must be verified in Resend (DNS records). For local operation (stdio or HTTP), Node.js is required. The hosted remote server requires no local installation step.
Features and Tools
The Resend MCP Server provides several tool groups according to the README and official documentation:
Sending emails: Send emails as HTML or plain text; add attachments as local files, URLs, or Base64; use CC, BCC, reply-to, scheduling, tags, custom headers, topic-based sending, and idempotency keys. Retrieve, update, cancel, or share sent emails via a share link. Batch-send multiple emails in a single call. Query delivery and engagement metrics for individual emails.
Receiving emails: List and read inbound emails. List and download attachments of received emails.
Templates: Create, list, get, update, publish, duplicate, and remove email templates. Compose template content with {{{VARIABLE}}} placeholders. Collaborate on drafts in the Resend dashboard's visual editor.
Contacts and audiences: Create, list, get, update, and remove contacts. Manage segment memberships and topic subscriptions. Import contacts in bulk via CSV. Create and manage custom contact properties.
Broadcasts: Create, send, cancel, list, get, update, and remove broadcast campaigns. List a broadcast's clicked links. Query recipients by event type (sent, delivered, opened, clicked, bounced, complained, unsubscribed, suppressed). Scheduling, personalisation placeholders, and preview text are supported.
Automations: Create, list, get, update, duplicate, and remove automations. Inspect individual automation runs. Send events to trigger automations for a contact. Create, update, and remove event definitions.
Domains: Create, list, get, update, remove, and verify sender domains. Configure tracking, TLS, and sending/receiving capabilities. Create and verify domain claims.
Segments and topics: Create, manage, and remove audience segments and subscription topics.
Suppression list: Add or remove individual or multiple recipients from the suppression list. Hard bounces and spam complaints are suppressed automatically; manual entries are possible for do-not-contact requests.
API keys and webhooks: Create, list, update, and remove API keys. Configure webhooks for event notifications and inspect their delivery history. Replay events to queue another delivery attempt.
Logs: List and inspect API request logs, including full request and response bodies.
Setup
Hosted remote server (recommended for interactive clients):
Claude Code: claude mcp add --transport http resend https://mcp.resend.com/mcp (OAuth login in the browser). Cursor: Settings > MCP > Add new global MCP server, URL https://mcp.resend.com/mcp. Codex: codex mcp add resend --url https://mcp.resend.com/mcp. For API key authentication instead of OAuth, pass a Resend API key as a Bearer token: claude mcp add --transport http resend https://mcp.resend.com/mcp --header "Authorization: Bearer re_xxxxxxxxx".
Local server (stdio, for CI/CD or headless agents):
claude mcp add resend -e RESEND_API_KEY=re_xxxxxxxxx -- npx -y resend-mcp. Cursor/Claude Desktop: JSON config with command: npx, args: ["-y", "resend-mcp"], and RESEND_API_KEY in env. Quick setup for all detected agents: npx add-mcp resend-mcp --name resend --env "RESEND_API_KEY=re_xxxxxxxxx".
Local HTTP server (for custom reverse proxy setups):
npx -y resend-mcp --http --port 3000 starts the server at http://127.0.0.1:3000/mcp. Clients pass the API key as a Bearer token in the Authorization header.
Security
The Resend MCP Server can send emails, modify contact data, and configure webhooks. API keys should be stored in environment variables or secure client configurations — not in publicly visible files or prompts. For local HTTP operation behind a reverse proxy, --host 0.0.0.0 or --allowed-hosts should be set correctly to ensure DNS-rebinding protection and proxy compatibility. Prompt injection via manipulated email content is a known risk for MCP servers with email access; agent outputs should be reviewed before any production email sending. Regularly review OAuth scopes in the Resend dashboard.
FAQ
Is the Resend MCP Server free? The server itself is MIT-licensed and open source. Usage depends on the chosen Resend plan. Current pricing information is published by Resend at https://resend.com/pricing.
Is OAuth mandatory? No. OAuth is the recommended path for interactive browser clients. All listed clients also support API key authentication for non-interactive or CI/CD environments.
Can I self-host the server? Yes. The MIT repository at https://github.com/resend/resend-mcp contains the TypeScript source code. Run pnpm install && pnpm run build to build a local instance and adapt it for your own deployments.
How current are the GitHub stars? The GitHub API reported exactly 567 stars on 2026-09-08. That number is a point-in-time snapshot of repository popularity and is not a security or quality promise.
Requirements
Resend account, MCP client (Claude Code, Claude Desktop, Codex, Cursor, etc.), and OAuth consent or a Resend API key. To send from a custom domain, the domain must be verified in Resend.
Installation instructions
Quick start
Hosted (remote): claude mcp add --transport http resend https://mcp.resend.com/mcp (OAuth login) or with API key header. Local (stdio): claude mcp add resend -e RESEND_API_KEY=re_xxxxxxxxx -- npx -y resend-mcp. Quick setup: npx add-mcp resend-mcp --name resend --env "RESEND_API_KEY=re_xxxxxxxxx".
claude mcp add --transport http resend https://mcp.resend.com/mcp
claude mcp add resend -e RESEND_API_KEY=re_xxxxxxxxx -- npx -y resend-mcp
npx add-mcp resend-mcp --name resend --env "RESEND_API_KEY=re_xxxxxxxxx"
What the Resend MCP Server is
The Resend MCP Server connects AI assistants to the Resend email platform via the Model Context Protocol, or MCP. MCP is an open standard that lets AI applications such as Claude, Cursor, or Claude Code access external tools and services in a structured way without building a custom integration for every application. According to the provider, the server lets you send and receive emails, manage contacts, create broadcasts, and administer domains directly from any MCP-capable client. Resend offers two variants for this: a remote server hosted by Resend itself, and the underlying open-source local server, available as a standalone package on npm, which can alternatively be self-hosted.
The hosted remote server
The easiest entry point is the server Resend hosts at a fixed address. Since no local process needs to run, this option works particularly well for web-based clients and hosted agent platforms. When connecting, the client opens a browser window where you log in to Resend and approve access via OAuth. For environments without a browser, such as servers or automated pipelines, a Resend API key can instead be set as a Bearer token in the authorization header. According to the provider's documentation, common clients including Claude Code, Claude itself, Cursor, Codex, GitHub Copilot in VS Code, Windsurf, and Warp are directly supported, each with its own configuration schema for establishing the connection.
The local server as an alternative
Anyone who prefers to run the server themselves, for example for privacy or control reasons, can start the local server via npx without a permanent install. The local server supports two transport modes: standard input/output as the default, and HTTP as an alternative. Running it requires a Resend API key generated in your own Resend account, plus a verified sending domain, since Resend only reliably delivers mail through verified domains. Configuration for most clients is a simple JSON structure containing the start command and the environment variable holding the API key. The local server is open source and also forms the technical foundation of the hosted offering, so functionality and behavior are largely identical between the two variants.
Setting it up in practice
For Claude Code, the remote server can be added as an HTTP transport with a single command, after which you complete the login through Claude Code's internal MCP command. For other clients, you enter the server address, or for the local server the start command and the API key, into that client's respective configuration file. Once connected, the AI assistant has the Resend tools available, so email sending, contact management, and domain administration can be driven directly from natural-language instructions without writing API calls yourself.
Security and limits
Because the server can actually send emails and modify account data, it is a tool with real external effects. An API key should therefore be treated like any other secret: not stored in plain text in shared configuration files or chat logs, and scoped as narrowly as possible if Resend offers such a restriction. With the OAuth variant, access control sits with Resend's own login system; with the API-key variant, responsibility for handling the key securely lies with whoever operates that environment. Especially in automated or multi-step agent workflows, it is worth manually confirming critical actions such as an actual send to a large recipient list before execution, to avoid misfired sends caused by misinterpreted instructions.
Who benefits from using it
Development teams that already use Resend as their sending infrastructure benefit the most, since recurring email tasks like transactional messages, status lookups, or domain maintenance can be integrated directly into an AI-assisted development workflow. For projects without an existing Resend account, adopting it only makes sense if you already plan to use Resend as your sending service, since the MCP server itself does not provide standalone mail delivery without a Resend account.
npx add-mcp resend-mcp --name resend --env "RESEND_API_KEY=re_xxxxxxxxx"
Authentication
OAuth (recommended for interactive browser clients) or Resend API key as a Bearer token (for CI/CD and non-interactive environments).
Required access permissions
Permissions follow the Resend account and the permission scope of the API key. Email sending, contact management, and domain configuration are possible.
Transmitted or stored data
Tool calls reach the Resend API and return structured results to the MCP client. Email content and contact data are transmitted to the Resend platform.
Security risks
Sending emails to arbitrary recipients, modifying contact data, domain configuration, API keys in insecure configurations, and prompt injection via manipulated email content.
License and costs
- License
- MIT
- Cost
- free
The server is MIT licensed. Costs depend on the chosen Resend plan. Current pricing information at resend.com/pricing.
Alternatives
Not recorded yet.
At a glance
- Provider
- Resend
- Status
- Official server
- Deployment
- Local and remote
- Current version
- Not recorded yet.
- GitHub stars
- 581
- Last reviewed
- 08.09.2026
Repository and documentation
Categories
Supported clients
Related guides
Guides and background related to this entry.
No related guides yet.