Resend MCP Server: Tools, Setup and Security

The Resend MCP server lets an AI agent send and receive email through Resend, run broadcast campaigns, and manage contacts, domains, templates, webhooks and even API keys. Resend publishes it in two forms: a hosted remote server and an open-source npm package you run yourself.

Checked against: Resend MCP server README on 28 October 2026. eSEOspace did not install or test this server.

At a glance

What it can do

Resend's README describes capability groups rather than a full list of tool names. In summary:

• Emails: send, batch send, list, get, cancel, update and share emails, with attachments, scheduling, tags and idempotency keys.
• Received emails and inboxes: read inbound email, manage inboxes and threads, reply to or forward threads, and create and send drafts.
• Broadcasts: create, send, cancel, schedule and remove campaigns, and see who opened, clicked or bounced.
• Contacts, segments, topics and properties: create, update and remove records and run CSV imports.
• Automations and events: create and run automations and send events that trigger them.
• Domains: create, verify, update and remove sender domains.
• Suppressions: add and remove do-not-contact entries.
• API keys and webhooks: create, update and remove keys; manage webhooks and replay deliveries.
• Logs and usage: inspect API request logs, including full request and response bodies, and check quotas.

Two tool names appear in the README: send-email and create-contact-import.

How to connect it

For the hosted server in Claude Code, Resend's README gives:

claude mcp add --transport http resend https://mcp.resend.com/mcp

Then run /mcp in Claude Code and select resend to finish the OAuth login. In Claude on the web or desktop, Resend says to open Settings > Connectors > Add custom connector and enter the URL.

For a server or CI job where a browser login is not possible, pass an API key:

claude mcp add --transport http resend https://mcp.resend.com/mcp --header "Authorization: Bearer re_xxxxxxxxx"

To run it locally over stdio instead:

claude mcp add resend -e RESEND_API_KEY=re_xxxxxxxxx -- npx -y resend-mcp

The README also has configs for Cursor, Codex, GitHub Copilot in VS Code, Windsurf (now Devin Desktop), Gemini CLI, OpenCode, Warp and Devin. For local use, you need a verified sending domain.

Security notes

This server has a wide blast radius. One prompt can send a broadcast to your whole list, delete a domain or create a new API key. Our page on excessive MCP permissions explains why that matters.

Points from Resend's README:

• Local file reads: send-email attachments and create-contact-import can read files from disk. Over --http this is off by default. On stdio, Resend advises setting --allowed-file-dirs "to stop a prompt-injected agent from attaching files outside the folders you choose."
• DNS rebinding: the local HTTP mode applies localhost-only Host validation by default. Resend explains how to set --host or --allowed-hosts behind a proxy.
• Sender defaults: set SENDER_EMAIL_ADDRESS so the agent uses an expected address.

The MCP tools specification says clients should prompt for confirmation on sensitive operations. Our own suggestions: use a restricted API key where your setup allows it, keep send and delete tools behind approval, and review the Logs tool output for sensitive request bodies. Attackers can plant instructions in inbound mail, so read about prompt injection through tool results. The MCP security center has more.

Alternatives

• Postmark MCP server, with MCP tool annotations that flag destructive tools.
• Mailgun MCP server, which exposes no delete operations.
• Mailtrap MCP server, with a sandbox for safe test sends.

Next step

If you want an agent to send product or onboarding email, separate test and production keys first. eSEOspace can help you design that workflow through our MCP development service. See other email servers in our MCP server directory.

Frequently asked questions