home / mcp / resend mcp server

Resend MCP Server

A MCP server for Resend API. Let LLMs compose and send emails for you.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "hawstein-resend-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resend-mcp"
      ],
      "env": {
        "RESEND_API_KEY": "YOUR_RESEND_API_KEY_HERE (string, required)",
        "SENDER_EMAIL_ADDRESS": "YOUR_SENDER_EMAIL_ADDRESS_HERE (string, required)",
        "REPLY_TO_EMAIL_ADDRESSES": "YOUR_REPLY_TO_EMAIL_ADDRESSES_HERE (string, optional, comma delimited)"
      }
    }
  }
}

You run a dedicated MCP server that lets you compose and send emails via the Resend API using your own prompts. It exposes a simple, secure way to specify sender details, recipient information, and optional reply-to addresses, while letting you trigger delivery on a schedule or attach files as needed.

How to use

You interact with the Resend MCP Server through an MCP client by selecting the resend MCP server you configured and issuing email send requests via the send_email tool. Provide the recipient, subject, and content, and optionally include from, replyTo, scheduledAt, and attachments. The server will handle authentication with your Resend API key and ensure emails are sent from your designated sender address.

How to install

Prerequisites: you need Node.js and npm installed on your machine. Ensure npm and npx are available in your environment.

Option 1: Install via Clinde (recommended)

1) Open the Clinde desktop app.

2) Go to the Servers page.

3) Find resend-mcp and click Install.

Option 2: Configure via Claude Desktop JSON (manual setup)

{
  "mcpServers": {
    "resend-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resend-mcp"
      ],
      "env": {
        "RESEND_API_KEY": "YOUR_RESEND_API_KEY_HERE (string, required)",
        "SENDER_EMAIL_ADDRESS": "YOUR_SENDER_EMAIL_ADDRESS_HERE (string, required)",
        "REPLY_TO_EMAIL_ADDRESSES": "YOUR_REPLY_TO_EMAIL_ADDRESSES_HERE (string, optional, comma delimited)"
      }
    }
  }
}

Additional setup notes

- Ensure yourResend API key is kept secure. Do not expose it in client-side code or public repositories.

- The SENDER_EMAIL_ADDRESS is used as the default From address if you do not specify one per email.

- REPLY_TO_EMAIL_ADDRESSES is optional and can contain a comma-delimited list of addresses to receive replies.

Security and maintenance

- Treat the Resend API key like a secret. Use environment variables to avoid leaking credentials in logs or code.

- Regularly review reply-to configurations to ensure responses are directed to appropriate channels.

Notes on tools and capabilities

The server exposes a send_email tool that lets you compose and send emails through the Resend API. Inputs include: - to: recipient email address - subject: email subject line - content: plain text body - from: sender address (optional, defaults to SENDER_EMAIL_ADDRESS) - replyTo: list of reply-to addresses (optional, defaults to REPLY_TO_EMAIL_ADDRESSES) - scheduledAt: optional delivery time - attachments: optional list with filename and either localPath or remoteUrl for the file to attach.

Examples and troubleshooting

If you encounter issues sending emails, verify that the RESEND_API_KEY and SENDER_EMAIL_ADDRESS are correctly set in your environment. Check that REPLY_TO_EMAIL_ADDRESSES is properly formatted if you use it. If you need to test attachments, ensure the file paths or URLs are accessible from the runtime environment.

Available tools

send_email

Send an email using the Resend API. Requires to, subject, content and optional from, replyTo, scheduledAt, and attachments.