Resend MCP Server
# Resend MCP Server
A Model Context Protocol (MCP) server for sending emails via the [Resend](https://resend.com) API. Designed for use with Claude Code and other MCP-compatible AI assistants.
## Features
- Send single emails with HTML or plain text content
- Send batch emails (up to 100 in one call)
- Support for CC, BCC, and reply-to addresses
- Custom tags for email tracking
- Platform-controlled sender address for security
## Installation
```bash
npm install @bugzy-ai/resend-mcp-server
```
Or run directly with npx:
```bash
npx @bugzy-ai/resend-mcp-server
```
## Configuration
Set the following environment variables:
```bash
RESEND_API_KEY=re_xxxxxxxxxxxxx
RESEND_FROM_EMAIL="Bugzy <notifications@yourdomain.com>"
```
## MCP Configuration
Add to your MCP configuration (e.g., `.mcp.json`):
```json
{
"mcpServers": {
"resend": {
"command": "resend-mcp-server",
"env": {
"RESEND_API_KEY": "${RESEND_API_KEY}",
"RESEND_FROM_EMAIL": "${RESEND_FROM_EMAIL}"
}
}
}
}
```
## Available Tools
### resend_send_email
Send a single email to one or more recipients.
**Parameters:**
- `to` (required): Email address(es) - string or array (max 50)
- `subject` (required): Email subject line
- `html` (optional): HTML content
- `text` (optional): Plain text content (one of html/text required)
- `cc` (optional): CC recipient(s)
- `bcc` (optional): BCC recipient(s)
- `reply_to` (optional): Reply-to address(es)
- `tags` (optional): Array of `{name, value}` for tracking
### resend_send_batch_emails
Send multiple emails in a single API call.
**Parameters:**
- `emails` (required): Array of email objects (max 100)
- Each email has the same parameters as `resend_send_email`
## Development
```bash
# Install dependencies
npm install
# Run in development mode
npm run dev
# Build for production
npm run build
# Lint code
npm run lint
```
## License
Apache-2.0
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose for sending emails.
The tool name follows a consistent verb_noun pattern (resend_send_email), and with only one tool, there is no inconsistency to evaluate. The naming is clear and predictable.
A single tool for an email server is too few for the apparent scope, as it lacks basic operations like listing emails, checking status, or managing templates. This limits functionality and may cause agent failures.
The tool surface is severely incomplete for an email domain; it only supports sending emails without any read, update, delete, or management capabilities. This creates significant gaps that will hinder agent workflows.