Resend MCP Server logo

Resend MCP Server

Connects AI clients to Resend for email, contact, broadcast, and domain management through hosted or self-hosted MCP.

Install Resend MCP Server

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "resend-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resend-mcp"
      ],
      "env": {
        "RESEND_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 11/11/2026, 12:00:31 AM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.resend.com/mcp

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Resend MCP Server connects MCP clients to Resend for sending and receiving email and managing contacts, broadcasts, and domains. Resend hosts a Streamable HTTP endpoint with browser-based OAuth, while the open-source npm package supports local stdio or HTTP operation. Use it when an agent needs to perform Resend account and email tasks, with API-key authentication available for headless or self-hosted deployments.

Use cases

  • Send transactional email from an AI workflow
  • Manage Resend contacts through an MCP client
  • Create and operate email broadcasts
  • Inspect and manage verified sending domains
  • Run Resend tools from a headless agent with an API key

Key features

  • Resend email operations
  • Contact and broadcast management
  • Domain management
  • Hosted OAuth authentication
  • Local stdio and Streamable HTTP transports
  • Configurable sender, reply-to, port, and host validation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars580Stargazers on the source repository.
Last commitTodayMost recent push to the default branch.

How Resend MCP Server works

What Resend MCP Server does

Resend MCP Server exposes Resend operations to AI agents through the Model Context Protocol. Its supported workflows include sending and receiving email, working with contacts, managing broadcasts, and managing domains. The hosted deployment is available at https://mcp.resend.com/mcp; the same open-source implementation can be launched locally from the resend-mcp npm package.

The server is suited to agents that need to act on a Resend account rather than only generate email content. A Resend API key and verified domain are needed for local operation. The hosted service can use OAuth, so clients can complete sign-in and authorization in a browser.

How it works

Two deployment models are available:

  • The remote server uses Streamable HTTP. MCP clients connect to Resend's hosted endpoint and authenticate through OAuth, or send a Resend API key as a Bearer token when browser login is unavailable.
  • The local package defaults to stdio and can be started with npx -y resend-mcp. It can also run as an HTTP service with the MCP endpoint at /mcp.

HTTP mode authenticates each client with a Resend API key in the Authorization header. The HTTP implementation can also be embedded in another Node service through its exported runHttp function. It provides /mcp over POST, GET, and DELETE, along with a /health endpoint.

Local HTTP mode applies localhost-only Host validation by default. Deployments behind a reverse proxy or load balancer can set a host or allowed-host list to handle forwarded hostnames.

Setup and configuration

For the hosted option, add https://mcp.resend.com/mcp to an MCP client that supports remote servers, then complete OAuth. The package includes setup examples for Claude Code, Claude, Cursor, Codex, VS Code with GitHub Copilot, Windsurf, Gemini CLI, Devin, and other clients.

For local stdio use, provide RESEND_API_KEY and launch the package through npx, or add it to the client's MCP configuration. A verified Resend domain is required. The default sender can be set with --sender, and one or more default reply-to addresses can be supplied with --reply-to.

Start HTTP mode with:

Terminal
npx -y resend-mcp --http --port 3000

The port can instead be set with MCP_PORT. HTTP deployments can configure host validation with MCP_HOST or MCP_ALLOWED_HOSTS. CLI options include --key for the API key in stdio mode, --http, --port, --host, and --allowed-hosts.

Tools and capabilities

  • Send and receive email through Resend
  • Manage Resend contacts
  • Create and manage broadcasts
  • Manage Resend domains
  • Authenticate hosted connections with OAuth
  • Authenticate headless and HTTP clients with Bearer API keys
  • Run through stdio or Streamable HTTP

Limitations and notes

The local server requires a Resend API key and a verified domain. In HTTP mode, the API key is supplied per request by the connecting client rather than configured as the server's stdio key. Local file attachments and CSV imports are restricted by allowed directories: stdio is unrestricted when no directory list is set, while HTTP access requires an explicit allowed-directory configuration.

When exposing HTTP mode through a proxy or load balancer, configure host validation appropriately. Setting the host to 0.0.0.0 disables Host validation; an explicit allowed-host list can be used instead. Keep API keys out of shared configuration and pass them through the client's protected environment or authorization settings.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Resend MCP Server

Resend MCP Server is an MCP server that connects AI clients to the Resend platform. Its main capabilities include sending and receiving emails, managing contacts, handling broadcasts, and managing domains. It is available as Resend's hosted Streamable HTTP endpoint or as the open-source resend-mcp package for local stdio or HTTP use.

Run it locally with `npx -y resend-mcp` and configure `RESEND_API_KEY` in your MCP client. You can also use Resend's hosted endpoint at `https://mcp.resend.com/mcp`, which requires no local installation. Local use requires a Resend API key and a verified domain.

Yes, Resend MCP Server works with Cursor. Add the hosted URL as a remote MCP server, or configure Cursor to run `npx -y resend-mcp` with `RESEND_API_KEY` for stdio. Local HTTP mode is also supported with the MCP URL and an Authorization Bearer token.

Start the package with `npx -y resend-mcp --http --port 3000`, then connect clients to `http://127.0.0.1:3000/mcp` using a Resend API key as a Bearer token. The port can be set with `MCP_PORT`, and the server also supports host and allowed-host configuration.

Yes, use a Resend API key as a Bearer token instead of OAuth. This supports server, CI, and headless-agent deployments for the hosted endpoint, and is also the authentication method used by local HTTP mode.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewResend MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/resend-mcp?style=directory)](https://allmcps.com/mcp/resend-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/resend-mcp"><img src="https://allmcps.com/api/badge/resend-mcp?style=directory" alt="Resend MCP Server on AllMCPs" /></a>