Skip to main content
Glama
enesjakozh
Hawstein

MCP Server Resend

by Hawstein
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

MCP Server Resend

A MCP server for Resend API. Let LLMs compose and send emails for you.

Environment Variables

  • RESEND_API_KEY (string, required): Your Resend API key

  • SENDER_EMAIL_ADDRESS (string, required): Sender email address

  • REPLY_TO_EMAIL_ADDRESSES (string, optional): Comma-separated list of reply-to email addresses

Related MCP server: Resend MCP Server

Available Tools

  • send_email - Send an email using the Resend API

    • Inputs:

      • to (string): Recipient email address

      • subject (string): Email subject line

      • content (string): Plain text email content

      • from (string, optional): Sender email address (uses SENDER_EMAIL_ADDRESS if not provided)

      • replyTo (array, optional): Reply-to email addresses (uses REPLY_TO_EMAIL_ADDRESSES if not provided)

      • scheduledAt (string, optional): Scheduled email delivery time

      • attachments (array, optional): List of attachments, each attachment must have:

        • filename (string): Name of the attachment file

        • localPath (string): Absolute path to a local file on user's computer (required if remoteUrl not provided)

        • remoteUrl (string): URL to a file on the internet (required if localPath not provided)

Getting an API Key

  1. Sign up for a Resend account

  2. Generate your API key from the Resend dashboard

Note: Free tier available with 3000 emails per month.

Installation

Using Clinde (recommended)

The easiest way to use Resend MCP Server is through the Clinde desktop app. Simply download and install Clinde, then:

  1. Open the Clinde app

  2. Navigate to the Servers page

  3. Find resend-mcp and click Install

That's it! No technical knowledge required - Clinde handles all the installation and configuration for you seamlessly.

Using Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "resend-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "resend-mcp"
      ],
      "env": {
        "RESEND_API_KEY": "YOUR_RESEND_API_KEY_HERE (string, required)",
        "SENDER_EMAIL_ADDRESS": "YOUR_SENDER_EMAIL_ADDRESS_HERE (string, required)",
        "REPLY_TO_EMAIL_ADDRESSES": "YOUR_REPLY_TO_EMAIL_ADDRESSES_HERE (string, optional, comma delimited)"
      }
    }
  }
}

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

1 tool
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.

ParametersJSON Schema
NameRequiredDescriptionDefault
attachmentsNoOptional. List of attachments. Each attachment must have a filename and either localPath (path to a local file) or remoteUrl (URL to a file on the internet).
contentYesPlain text email content
fromNoOptional. If provided, uses this as the sender email address; otherwise uses SENDER_EMAIL_ADDRESS environment variable
replyToNoOptional. If provided, uses these as the reply-to email addresses; otherwise uses REPLY_TO_EMAIL_ADDRESSES environment variable
scheduledAtNoOptional parameter to schedule the email. This uses natural language. Examples would be 'tomorrow at 10am' or 'in 2 hours' or 'next day at 9am PST' or 'Friday at 3pm ET'.
subjectYesEmail subject line
toYesRecipient email address

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions features like attachments and scheduling but lacks critical details: it doesn't specify authentication requirements (e.g., API keys), error handling, rate limits, or what happens on success/failure. For a tool that sends emails, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured in two sentences, with no wasted words. It front-loads the core purpose and efficiently lists key features. However, it could be slightly more informative without losing conciseness, such as by hinting at behavioral aspects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of an email-sending tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It lacks essential context like authentication needs, error handling, rate limits, and response format. This makes it inadequate for an agent to use the tool reliably in varied scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds minimal semantic value beyond the input schema, which has 100% coverage. It mentions 'plain text content, attachments and optional scheduling' and 'custom sender and reply-to addresses,' but these are already covered in the schema descriptions. No additional syntax or constraints are provided, so it meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Sends an email using the Resend API.' It specifies the action (send) and resource (email), and mentions key capabilities like plain text content, attachments, and scheduling. However, without sibling tools, there's no need for differentiation, so it doesn't score a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It lists features but doesn't specify scenarios, prerequisites, or exclusions. For example, it doesn't mention when scheduling might fail or if there are rate limits, leaving the agent with minimal usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • IMAP MCP Server

    nikolausm
    A
    license
    A
    quality
    A
    maintenance
    Enables Claude to interact with email accounts via IMAP and SMTP, providing tools for searching, reading, sending, and managing emails across multiple providers.
    40
    604
    90
    MIT

  • Resend MCP Server

    universal-mcp
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables sending emails and managing email delivery through Resend's API, allowing users to compose and send emails using natural language.
    1
    MIT

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hawstein/resend-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server