resend
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESEND_API_KEY | Yes | Your Resend API key. Get it from https://resend.com/settings/api |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailB | Send an email via Resend. |
| get_emailB | Get email details including delivery status. |
| list_emailsB | List sent emails with pagination. |
| create_contactB | Create a new contact. |
| get_contactA | Get a single contact by ID. |
| list_contactsA | List contacts with optional segment filtering. |
| update_contactC | Update an existing contact. |
| delete_contactC | Remove a contact. |
| list_segmentsA | List all contact segments. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| skill_usage | Usage guide for the Resend MCP server tools. |
TDQS
Scored across 9 tools
Each tool targets a distinct resource and action: contacts have CRUD operations, emails have send/get/list, and segments have list. No ambiguity exists between tools.
All tools use a consistent verb_noun pattern in snake_case (e.g., create_contact, send_email, list_contacts), making actions clear and predictable.
9 tools is ideal for the server's purpose, covering email sending and contact management without unnecessary bloat or missing core functionality.
Contacts have full CRUD, emails support send and retrieval, and segments are listable. The only gap is lack of segment management (create/update/delete), which is a minor workaround for most use cases.