Website
Resend
Transactional email service. Send emails from your website using Resend.
🔑 Setup Required — Bring Your Own Key
This integration requires API credentials. Store them once via
setup_integration or the Dashboard Vault — they're encrypted
with AES-256-GCM and never exposed.
Required Credentials
resend_api_key
API Key
Find your API key at resend.com/api-keys
Get your API key at resend.com →
Endpoints (1)
POST
send-email
Send a transactional email
| Field | Type | Required | Description |
|---|---|---|---|
from |
string | ✓ Yes | Sender email address (e.g. "Name <noreply@yourdomain.com>") |
to |
string|array | ✓ Yes | Recipient email address(es) |
subject |
string | ✓ Yes | Email subject line |
html |
string | No | HTML body content |
text |
string | No | Plain text body content (fallback) |
reply_to |
string|array | No | Reply-to email address(es) |
cc |
string|array | No | CC recipient(s) |
bcc |
string|array | No | BCC recipient(s) |
attachments |
array | No | File attachments: [{ filename, content_base64 }]. content_base64 is required per item; omitting it returns 422 ATTACHMENT_MISSING_CONTENT. A mime_type key is accepted but ignored for Resend — this manifest declares no map[type] (see the attachments block below), so the value is dropped and Resend infers the content type from the file extension. |
MCP Tool Names
When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:
| Endpoint | MCP Tool Name |
|---|---|
| send-email | resend_send_email |