Resend

Resend's MCP server covers close to the whole Resend API, not just a send-email tool. That matters because the interesting agent workflows are the ones after the send: reading the request log to see why a message bounced, checking domain verification, adding an address to the suppression list, or drafting a broadcast against a segment.

Coverage

• Emails — send, list, get, cancel, update and batch send. HTML or plain text, attachments from a local file, URL or base64, CC/BCC, reply-to, scheduling, tags, custom headers, topic-based sending and idempotency keys.
• Received emails — list and read inbound mail, list and download inbound attachments.
• Templates — create, update, publish, duplicate and remove, with {{{VARIABLE}}} placeholders.
• Contacts, segments, topics and contact properties — including CSV imports, segment membership and custom attributes.
• Broadcasts — create, schedule, send, cancel and manage campaigns with personalisation and preview text.
• Automations and events — define automations and fire events that trigger them for a contact.
• Domains — create, verify and configure sender domains including tracking, TLS and send/receive capabilities.
• Suppressions — hard bounces and spam complaints are suppressed automatically; add addresses manually to honour do-not-contact requests.
• API keys, webhooks and logs — including full request and response bodies for debugging.
• Editor — connect to the visual editor in the Resend dashboard and read a draft while collaborating on a broadcast or template.

Two ways to run it

The remote server at https://mcp.resend.com/mcp needs nothing installed and uses OAuth — your client opens a browser to log in and approve access. That is the better option for web-based clients and hosted agents. The same open-source code is published on npm as resend-mcp if you would rather run it yourself over stdio or HTTP, using an API key.

Worth knowing

This server sends real email to real people and can manage your sending domains and API keys. Use a scoped Resend API key, verify your domain first, and be deliberate about which agents get write access.