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 (e.g., re_xxxxxxxxxxxxx) | |
| RESEND_FROM_EMAIL | Yes | The sender email address with optional name (e.g., "Bugzy <notifications@yourdomain.com>") |
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 |
|---|---|
| resend_send_emailB | Send a single email to one or more recipients. Supports HTML and plain text content, CC/BCC, reply-to, and custom tags for tracking. |
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 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.