MCP Server Resend
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RESEND_API_KEY | Yes | Your Resend API key | |
| SENDER_EMAIL_ADDRESS | Yes | Sender email address | |
| REPLY_TO_EMAIL_ADDRESSES | No | Comma-separated list of reply-to email addresses |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_emailC | Sends an email using the Resend API. Supports plain text content, attachments and optional scheduling. Can specify custom sender and reply-to addresses. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'send_email' has a clear, singular purpose that cannot be confused with any other tool in this set.
The single tool name 'send_email' follows a clear verb_noun pattern, and since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'MCP Server Resend', which implies a broader email-related domain. While 'send_email' is a core function, the lack of tools for operations like listing emails, checking status, or managing templates makes the set feel incomplete and under-scoped.
The tool set is severely incomplete for an email service domain. It only provides a 'send' operation, with no tools for reading, updating, deleting, or managing emails or related resources, which are essential for typical email workflows and will likely cause agent failures in broader tasks.