Resend MCP Server
Send and manage emails, contacts, and domains directly within AI agent environments.
Data last scanned yesterday · Reviewed last month
Overview
The Resend MCP Server facilitates deep integration between your AI agents and the Resend email platform. Users can perform actions such as sending emails, managing contact lists, overseeing broadcasts, and configuring domains by issuing commands from compatible MCP clients like Claude, Cursor, and Claude Code. The server is available in both a hosted remote format and a local package. The remote version simplifies setup by removing the need for local process management, relying on OAuth for secure authentication in browser-based AI environments, while the local TypeScript implementation offers more granular control for self-hosted configurations.
Our verdict
With a security score of 45/100, this project carries a high risk level. Key concerns include the fact that the project is not officially maintained by the vendor and its OAuth and read-only support mechanisms have not yet undergone an editorial security review. It is best suited for developers comfortable managing third-party tools that handle sensitive email communications.
- Supports both remote hosted and local deployment modes
- Small dependency footprint with only six direct packages
- Active development with commits within the last day
- Twenty-four contributors reduce single-point-of-failure risks
- Community-maintained rather than official vendor software
- Lacks editorial verification of security implementation
- No homepage link provided in repository metadata
Setup
{
"mcpServers": {
"resend-mcp": {
"args": [
"-y",
"resend-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| send_email | Send an email. | medium |
| list_emails | List emails. | low |
| get_email | Get an email. | low |
| cancel_email | Cancel an email. | medium |
| update_email | Update an email. | medium |
| batch_send_email | Batch send emails. | medium |
| list_received_emails | List inbound emails. | low |
| get_received_email | Read an inbound email. | low |
| list_received_email_attachments | List received email attachments. | low |
| download_received_email_attachment | Download a received email attachment. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›Can I use the Resend MCP server without installing software locally?
Yes, you can use the hosted remote MCP server at https://mcp.resend.com/mcp, which requires no local installation or process management.
›How do I authenticate if my client cannot open a browser for OAuth?
For headless environments like servers or CI pipelines, you can authenticate by passing your Resend API key as a Bearer token in the Authorization header.
›What are the requirements for using the local MCP server?
To run the local server, you must create a Resend API key and verify your domain within your Resend account.
›Does the local MCP server support multiple transport modes?
Yes, the local server supports both stdio (the default) and HTTP transport modes.
Alternatives
Changelog
Badge
Maintain this server? Add the live badge to your README.