Resend MCP Server

Resend MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. .

What you get

Connect your AI agent to the Resend platform. Send and receive emails, manage contacts, broadcasts, domains, and more, directly from any MCP client like Claude, Cursor, or Claude Code.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Resend is connected, these are the calls the assistant has available:

• Emails — Send, list, get, cancel, update, and batch send emails. Supports HTML, plain text, attachments (local file, URL, or base64), CC/BCC, reply-to
• Templates — Create, list, get, update, publish, duplicate, and remove email templates. Supports composing template content and {{{VARIABLE}}} placeholders
• Contacts — Create, list, get, update, and remove contacts. Manage segment memberships, topic subscriptions, and CSV contact imports. Supports custom contact
• Broadcasts — Create, send, list, get, update, and remove broadcast campaigns. Supports scheduling, personalization placeholders, and preview text
• Automations — Create, list, get, update, and remove automations. Review the runs of an automation
• Events — 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
• Segments — Create, list, get, and remove audience segments
• Suppressions — List, get, add, and remove suppression list entries, individually or in batch. Hard bounces and spam complaints are suppressed automatically; add
• Topics — Create, list, get, update, and remove subscription topics
• Webhooks — Create, list, get, update, and remove webhooks for event notifications
• Logs — List and inspect API request logs, including full request and response bodies

Configuration and credentials

You will need 2 environment variables: RESEND_API_KEY, SENDER_EMAIL_ADDRESS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Resend.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the resend mcp server does with a few real requests.

Choosing this one

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Resend's toolset — Emails, Templates, Contacts and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Resend's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.