---
title: "Resend MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/resend/
description: "Exposes real transactional-email and broader account operations; workflows must distinguish message approval, API acceptance, delivery evidence and data-sharing permissions."
---

# Resend MCP: review, setup & limitations · Undominated.ai

> Exposes real transactional-email and broader account operations; workflows must distinguish message approval, API acceptance, delivery evidence and data-sharing permissions.

[← Explore all mcp servers](/mcp-servers/)

EMAIL OPERATIONS / Resend

# Resend MCP

Exposes real transactional-email and broader account operations; workflows must distinguish message approval, API acceptance, delivery evidence and data-sharing permissions.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/resend/resend-mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 9 linked sources
 Publisher Resend
 Licence [MIT ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/LICENSE)
 Revision 0047400a8ece
 [Read what was—and wasn’t—checked ↓](#review)

“Connect your AI agent to the Resend platform.”

 [Resend · upstream description ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The actual send handler exposes recipients, text/HTML, optional scheduling, attachments and idempotency keys, so an approval handoff can name exactly what will be sent.
- Separate retrieval/listing tools expose email IDs and status evidence, while registration and API-key handlers reveal authority beyond drafting or sending.

### A good fit for

 - Preparing an explicitly approved transactional message from a configured sender, with bounded recipients, content, attachment provenance and a retry identity.
- Inspecting a known message's returned ID and delivery status after a separately authorized send; source review itself supplies no send or delivery receipt.

### Weigh up before choosing

 - All registered account groups are broader than email drafting: sends, broadcasts, contacts, domains, webhooks, API keys and other mutations may be available under the connected identity. Tool-description confirmation instructions are not a server-side approval state machine.
- Stdio local file reads are unrestricted when the allow-list is unset. An empty --allowed-file-dirs or MCP_ALLOWED_FILE_DIRS string parses to undefined, not the empty array that disables reads; do not use a blank value as a deny-all control.
- Attachment inputs can specify several sources; the handler selects filePath before url before content rather than enforcing exactly one. The advertised total-size limit is description text, not a local byte-count guard in the inspected handler.
- Send success text reflects a successful API response, not delivery. Retrying without a deliberate idempotency key can duplicate external effects; batch sends and broadcasts are distinct operations.
- share-email creates an unauthenticated-viewer link according to its tool contract. Email bodies, raw-download URLs and newly created API-key tokens can reach the agent's result/transcript surface.
- Local HTTP uses app.listen(port) without a bind address; --host controls Host validation, not interface binding. In the legacy session branch, an existing session ID is reused without a bearer-token recheck in this file; SDK/proxy enforcement was not audited.
- The hosted endpoint is not pinned to this commit, and local npx setup is unversioned. package.json declares Node >=22 and a prepare build; package tarballs, SDK internals and dependency advisories were not audited.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md, package.json and LICENSE
- src/index.ts, src/cli/resolve.ts and src/cli/parse.ts
- src/server.ts
- src/tools/emails.ts in full
- src/tools/apiKeys.ts
- src/lib/safe-access.ts
- src/transports/http.ts

### Our findings

 - send-email requires to (one to 50 addresses), subject and text; html is optional and from is required when no sender is configured. Optional idempotencyKey is passed to the SDK. Output is text containing the API response data, not a durable delivery-verification record.
- list-emails enforces exclusive after/before pagination and returns summaries with IDs and last-event status; get-email returns message details and body text. Scheduled update/cancel calls and share-email are separate mutations, not draft preparation.
- readAllowedFile resolves paths against real allowed directories when configured. Undefined permits all paths, [] rejects reads; HTTP defaults to [], while the CLI list parser turns blank lists into undefined.
- The server registers administration groups without a per-group allowlist in createMcpServer. create-api-key returns the created token; the reviewed removal handler calls the SDK after instructions to ask the user, without an approval parameter.
- The HTTP modern branch obtains credentials per request, while the legacy branch attaches credentials at initialization and reuses sessions by ID. This is a source-level boundary requiring further deployment review, not a reproduced exploit or a hosted-service finding.
- The package's prepare hook runs its TypeScript build/chmod command. Direct dependencies include MCP server/node/express 2.0.0, resend 6.31.0, express 5.2.1, zod 4.4.3, dotenv 17.4.2 and minimist 1.2.8; no installed graph or advisory status was measured.
- The original MIT source decision, hosted install command/config and source revision are retained. No account connection or external communication was made.

### Not established by this review

 - No package installation, prepare script, server, MCP session, OAuth flow, API-key operation, email, attachment read, sharing link or delivery check was executed.
- No SDK/session-isolation, hosted deployment, remote URL-fetch policy, contact-import/editor/other account-handler or transitive-dependency security audit. Source observations are not runtime certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/README.md)

DOCUMENTED COMMAND

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

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - The command configures Resend’s hosted service in Claude Code; open /mcp and complete OAuth.
- The JSON example is for Cursor. Use the publisher’s matching guide for other clients.
- For local stdio, provide RESEND_API_KEY securely to the documented npx -y resend-mcp process and verify the sending domain before sending.

### Before you start

 - A Resend account with the required sending/domain permissions and an appropriate MCP client.
- For local execution, a compatible Node.js runtime and a Resend API key.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "resend": {
 "url": "https://mcp.resend.com/mcp"
 }
 }
} Copy configuration ↗

### Compatibility

Hosted Streamable HTTP with OAuth or an API key; the example is the documented Cursor configuration. · Local stdio clients or the documented self-hosted HTTP alternative.

### Implementation

TypeScript

### Transports

stdio · Streamable HTTP

### Resend account / real email and account writes

 - Read account/email data and exercise the operations permitted by the authenticated Resend identity; registration is not limited to send-only tools.
- Send or schedule messages and batches, attach local/remote/base64 content and create public-viewer links when separately authorized.
- API-key creation exposes a new token to the tool result. Email bodies and attachment/raw-email download URLs also require private handling.

### Cost model

Resend’s email and account plans, usage allowances and applicable overages govern service costs; the MIT source licence does not include delivery service.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned hosted/local setup and original config ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/README.md) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/README.md Supports: upstreamDescription, install, compatibility, transports, configExample
- [Actual message schemas and handlers ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/tools/emails.ts) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/tools/emails.ts Supports: summary, whySelected, bestFor, review, limitations, access
- [File-access policy helper ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/lib/safe-access.ts) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/lib/safe-access.ts Supports: review, limitations, access
- [Allow-list parsing ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/cli/parse.ts) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/cli/parse.ts Supports: review, limitations
- [Tool-group registration ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/server.ts) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/server.ts Supports: review, limitations, access
- [API-key administration handlers ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/tools/apiKeys.ts) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/tools/apiKeys.ts Supports: review, limitations, access
- [HTTP credential and session branches ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/transports/http.ts) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/transports/http.ts Supports: review, limitations
- [Runtime, lifecycle and dependency manifest ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/package.json) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/package.json Supports: review, limitations
- [Source licence ↗](https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/LICENSE) Checked 2026-10-14 https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/LICENSE Supports: license

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Intercom MCP Server ↗ Hosted Intercom endpoint for searching conversations, contacts and companies and fetching full records. Intercom’s developer page also lists Help Center article writes and internal notes.](/mcp-servers/intercom/)[### Airtable MCP Server ↗ Hosted Airtable server exposing bases, records, tables, interfaces and automations as tools over Streamable HTTP. Every connection is scoped to authorised bases and the server enforces existing Airtable permissions, so a read-only base stays read-only through MCP.](/mcp-servers/airtable/)[### Algolia MCP Server ↗ Algolia's managed MCP offerings: Public MCP exposes application-scoped search and recommendations on selected indices for customer-facing agents; Productivity MCP gives user-scoped, read-only exploration and analytics; DevEx MCP serves version-matched API client snippets to coding agents without touching data.](/mcp-servers/algolia/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
