Labsco
MCP SERVER · OFFICIAL PROJECT

Resend Email

by resend ↗

Run a Resend account from an agent: send and read mail, manage contacts and segments, build broadcasts, verify domains, and read the API logs.

Email: Mailboxes & Delivery✓ Official source
Summary
Not a send-email tool — the whole Resend account, including the parts you would normally open the dashboard for.

Sending is the small half. What makes this worth wiring up is everything around a send: domain verification, suppression hygiene, segment membership, and request logs carrying full request and response bodies, so an agent chasing a delivery problem reads the actual API exchange instead of guessing at it. The hosted endpoint takes OAuth and installs nothing, which is the right default for web clients; the local build exists for CI and headless agents.

What it is

Resend's own MCP server for its email platform, hosted by Resend at https://mcp.resend.com/mcp and published on npm as resend-mcp if you would rather run the same open-source code yourself. Coverage goes well past sending: inbound mail, templates, contacts, broadcasts, automations, domains, suppressions, webhooks, and request logs.

What you get
  • Sending: single and batch, HTML or plain text, attachments from a local file, a URL, or base64, CC and BCC, reply-to, scheduling, tags, custom headers, and idempotency keys
  • Inbound mail: list and read received messages, and download their attachments
  • Broadcasts: compose, schedule, send, then read the clicked links and the recipients by event — sent, delivered, opened, clicked, bounced, complained, unsubscribed, suppressed
  • Contacts with custom properties, CSV imports, segment membership, and topic subscriptions
  • Templates with placeholder variables, publishable and duplicable
  • Domains: create, verify, claim, and configure tracking, TLS, and sending or receiving capability
  • Suppressions individually or in batch, on top of the hard bounces and spam complaints that are suppressed automatically
  • Automations and the events that trigger them, webhooks for notifications, and API request logs including full request and response bodies
Requirements

A Resend account. On the hosted endpoint your client opens a browser to log in and approve access over OAuth; where a browser is not possible, pass a Resend API key as a Bearer token instead. Running it yourself needs an API key and a verified domain: npx -y resend-mcp over stdio with RESEND_API_KEY set, or npx -y resend-mcp --http --port 3000 to serve Streamable HTTP at /mcp, where each connecting client supplies its own key. SENDER_EMAIL_ADDRESS sets a default from-address; without one the server asks for a sender on every call. Behind a reverse proxy, --host or --allowed-hosts widens the localhost Host check that otherwise answers 403.

Setup effort

One command plus a key — npx add-mcp resend-mcp --name resend --env "RESEND_API_KEY=re_xxxxxxxxx", then supply credentials