- Home
- MCP servers
- MCP Resend Email Server
MCP Resend Email Server
- typescript
0
GitHub Stars
typescript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"deploya-labs-mcp-resend": {
"command": "node",
"args": [
"ABSOLUTE_PATH_TO_MCP_SERVER/build/index.js",
"--key=YOUR_RESEND_API_KEY",
"--sender=OPTIONAL_SENDER_EMAIL_ADDRESS",
"--reply-to=OPTIONAL_REPLY_TO_EMAIL_ADDRESS_ONE",
"--reply-to=OPTIONAL_REPLY_TO_EMAIL_ADDRESS_TWO"
],
"env": {
"RESEND_API_KEY": "YOUR_API_KEY",
"SENDER_EMAIL_ADDRESS": "OPTIONAL_SENDER_EMAIL_ADDRESS",
"REPLY_TO_EMAIL_ADDRESSES": "OPTIONAL_REPLY_TO_EMAIL_ADDRESSES_COMMA_DELIMITED"
}
}
}
}This MCP server enables you to send emails through Resend directly from Cursor or Claude Desktop. By wiring an MCP client to this server, you can compose emails and dispatch them with a simple command, eliminating copy-paste steps and speeding up email workflows.
How to use
After you configure the MCP server, you can connect it from your MCP client (Cursor or Claude Desktop) and trigger email sends from chat or documents. You will supply a Resend API key and optional sender/reply-to addresses. Use the provided command templates to run the MCP server locally and expose it to your client.
How to install
Prerequisites: Node.js installed on your machine. You will also need npm (comes with Node.js) to install dependencies and build the MCP server.
Step 1: Install dependencies and build the MCP server.
npm install
npm run build
Configuration and usage notes
Two MCP server configurations are shown. Each config runs as a local process and is started with the node runtime, pointing to the built MCP server script.
Cursor integration uses a command line that passes your API key and optional sender and reply-to addresses.
Claude Desktop integration uses a similar setup but exposes the configuration as an MCP JSON snippet that can be loaded into Claude.
When you run the server, ensure you replace placeholders with your actual values.
Example configurations
{
"mcpServers": {
"resend": {
"command": "node",
"args": [
"ABSOLUTE_PATH_TO_MCP_SERVER/build/index.js",
"--key=YOUR_RESEND_API_KEY",
"--sender=OPTIONAL_SENDER_EMAIL_ADDRESS",
"--reply-to=OPTIONAL_REPLY_TO_EMAIL_ADDRESS_ONE",
"--reply-to=OPTIONAL_REPLY_TO_EMAIL_ADDRESS_TWO"
],
"env": {
"RESEND_API_KEY": "YOUR_API_KEY",
"SENDER_EMAIL_ADDRESS": "OPTIONAL_SENDER_EMAIL_ADDRESS",
"REPLY_TO_EMAIL_ADDRESSES": "OPTIONAL_REPLY_TO_EMAIL_ADDRESSES_COMMA_DELIMITED"
}
}
}
}
Security and keys
Keep your Resend API key secret. Do not commit it to version control. Use environment variables to avoid exposing sensitive values in scripts or configuration files.
Troubleshooting
If emails fail to send, verify that your Resend API key is valid and has permission to send from the selected sender address. Confirm that the sender and reply-to addresses are correctly configured.
Available tools
sendEmail
High-level tool to dispatch an email via Resend using the provided API key, sender, and reply-to addresses. Integrates with the MCP to trigger email sends from Cursor or Claude Desktop workflows.