← Explore all 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.

“Connect your AI agent to the Resend platform.”

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.

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 ↗

DOCUMENTED COMMAND

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

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

  1. The command configures Resend’s hosted service in Claude Code; open /mcp and complete OAuth.
  2. The JSON example is for Cursor. Use the publisher’s matching guide for other clients.
  3. 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"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/README.md

    Supports: upstreamDescription, install, compatibility, transports, configExample

  2. https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/tools/emails.ts

    Supports: summary, whySelected, bestFor, review, limitations, access

  3. https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/lib/safe-access.ts

    Supports: review, limitations, access

  4. Allow-list parsing ↗Checked

    https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/cli/parse.ts

    Supports: review, limitations

  5. Tool-group registration ↗Checked

    https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/server.ts

    Supports: review, limitations, access

  6. https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/tools/apiKeys.ts

    Supports: review, limitations, access

  7. https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/src/transports/http.ts

    Supports: review, limitations

  8. https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/package.json

    Supports: review, limitations

  9. Source licence ↗Checked

    https://github.com/resend/resend-mcp/blob/0047400a8ece61aec7742d0850ea256cfcddabad/LICENSE

    Supports: license

Evidence & Ask