Resend MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESEND_API_KEY | Yes | Your Resend API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailB | Send a transactional email via Resend |
| list_emailsC | List recent emails sent via Resend |
| get_emailB | Get details about a specific email by ID |
| create_domainB | Create a new sending domain in Resend |
| list_domainsA | List all sending domains in your Resend account |
| verify_domainB | Trigger verification of a domain's DNS records |
| create_api_keyA | Create a new Resend API key (token is only returned once) |
| list_api_keysA | List all API keys in your Resend account (tokens are hidden) |
| list_contactsB | List contacts in a Resend audience |
| create_contactB | Add a new contact to a Resend audience |
| send_batch_emailA | Send multiple transactional emails in a single API call (up to 100) |
| list_audiencesB | List all audiences in your Resend account |
| create_audienceB | Create a new audience for organizing contacts |
| get_contactB | Get details about a specific contact by ID |
| update_contactC | Update an existing contact's properties |
| delete_contactC | Remove a contact from an audience |
| delete_api_keyB | Delete a Resend API key by ID |
| delete_domainB | Remove a sending domain from your Resend account |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action. Send_email vs send_batch_email are clearly differentiated by batch vs single. CRUD operations for each resource are separate and unambiguous.
All tool names follow a consistent verb_noun pattern using lowercase snake_case (e.g., create_api_key, list_domains). No mixing of styles or inconsistent verbs.
18 tools cover the main resources of an email service (API keys, audiences, contacts, domains, emails) without being excessive. Each tool serves a clear purpose.
The tool surface provides full CRUD for API keys (create, list, delete), domains (create, list, delete, verify), audiences (create, list), contacts (create, list, get, update, delete), and emails (send, send_batch, get, list). No obvious gaps for typical email API operations.