Resend MCP Server

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.

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.

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".

npx add-mcp resend-mcp --name resend --env "RESEND_API_KEY=re_xxxxxxxxx"

OAuth (recommended for interactive browser clients) or Resend API key as a Bearer token (for CI/CD and non-interactive environments).

Permissions follow the Resend account and the permission scope of the API key. Email sending, contact management, and domain configuration are possible.

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.

Sending emails to arbitrary recipients, modifying contact data, domain configuration, API keys in insecure configurations, and prompt injection via manipulated email content.