---
title: "Resend MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/resend/
description: "Connects an assistant to Resend email sending, delivery records and account operations through hosted or local MCP."
---

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

> Connects an assistant to Resend email sending, delivery records and account operations through hosted or local MCP.

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

EMAIL OPERATIONS / Resend

# Resend MCP

Connects an assistant to Resend email sending, delivery records and account operations through hosted or local MCP.

 See setup guidance ↓Original source ↗

SOURCE REVIEW

 Reviewed 2026-09-21
 Evidence 9 linked sources
 Publisher Resend
 Licence MIT ↗
 Revision e6f9faa56ab0
 Read what was—and wasn’t—checked ↓

“Connect your AI agent to the Resend platform.”

 Resend · upstream description ↗ Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Adds a concrete outbound-email workflow, including message inspection and scheduled-email operations.
- The current publisher implementation can be inspected alongside hosted OAuth setup, making its broader account permissions visible.

### A good fit for

 - Inspecting Resend delivery information while preparing a transactional-email workflow.
- Sending or scheduling an explicitly approved message from a configured Resend domain.

### Weigh up before choosing

 - This is broader than an email drafting tool: enabled operations can send real messages and administer contacts, broadcasts, domains and API keys.
- The local send handler can read an attachment from a supplied file path and transmit it; use an appropriately restricted process and credentials.
- Source review does not establish a confirmation gate before sending, deliverability or secure public self-hosting. Prefer the documented hosted connection unless you can manage the local service boundary.

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: current package identity, hosted OAuth endpoint and client-specific setup.
- package.json, src/index.ts and src/cli/resolve.ts: executable, runtime and credential requirements.
- src/server.ts, src/tools/emails.ts and src/transports/http.ts: tool registration, sends, attachments and HTTP sessions.
- LICENSE: MIT for repository source.
- src/tools/apiKeys.ts: key creation, listing and removal tools.

### Our findings

 - The server registers administration tool groups as well as email tools, so a narrow send-only description would omit material authority.
- The send handler reads filePath attachments with fs.readFile and calls resend.emails.send; client-side review must happen before that tool executes.
- Stdio requires RESEND_API_KEY at startup. HTTP uses connecting-client credentials; the hosted OAuth path is documented separately.
- The API-key creation tool returns the newly created token in its MCP result, so key administration also exposes credentials to the connected host.
- The local HTTP source calls app.listen(port) without a bind address even though its log prints a loopback URL; that log is not evidence of network isolation.

### Not established by this review

 - No server, account connection, email send, attachment access, delivery flow or authentication isolation was executed.

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 ↗

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

 - Reads email and account information permitted by the authenticated Resend identity.
- Can send messages, access local attachments in local mode and perform account mutations through registered tools.
- API-key creation can return a new credential in the tool result.

### 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.

 - Current server identity and setup ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/README.md Supports: upstreamDescription, descriptionSourceUrl, summary, whySelected, bestFor, install, compatibility, transports, configExample, access
- Registered account tool groups ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/src/server.ts Supports: summary, whySelected, review, access, limitations
- Email and attachment implementation ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/src/tools/emails.ts Supports: bestFor, review, access, limitations
- Credential configuration ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/src/cli/resolve.ts Supports: review, install, access
- HTTP transport implementation ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/src/transports/http.ts Supports: review, transports, limitations
- Package manifest ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/package.json Supports: language, install.prerequisites
- Resend service plans ↗ Checked 2026-09-21 https://resend.com/pricing Supports: access.cost
- Repository licence ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/LICENSE Supports: license
- API-key administration tools ↗ Checked 2026-09-21 https://github.com/resend/resend-mcp/blob/e6f9faa56ab014e883739c160433f96e55c98eff/src/tools/apiKeys.ts Supports: access, limitations, review

KEEP COMPARING

## Other approaches to consider.

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

 [### Asana MCP V2 ↗ Asana’s current workspace-scoped MCP connection for task, project and portfolio workflows.](/mcp-servers/asana/)[### Canva MCP ↗ A hosted connection for authorized Canva design discovery, creation, editing and export workflows.](/mcp-servers/canva/)[### GitHub MCP Server ↗ Connects an assistant to repository, issue, pull-request and workflow operations with selectable toolsets and account permissions.](/mcp-servers/github/)

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