Resend MCP Server: Setup Guide, Use Cases & Limitations

What Is Resend MCP Server?

Resend MCP Server connects Claude Code to the Resend API, enabling you to send transactional emails, manage templates, and work with email data directly from your Claude session. It is maintained by the Resend team and hosted under their official GitHub organization.

Quick Facts

What You Can Do With It

• Email sending: Trigger transactional emails (receipts, notifications, password resets) to individual recipients via natural language prompts or structured instructions.
• Template management: Create, update, and retrieve email templates stored in your Resend account without leaving your Claude session.
• Deliverability analytics: Query send metrics and delivery status data to diagnose bounce rates or check campaign performance.
• Bulk emails: Initiate bulk email sends to multiple recipients, leveraging Resend’s API batching where supported.

How to Set It Up

Prerequisites: A Resend account with an active API key. Generate one at resend.com/api-keys.

Step 1 — Verify the package runs locally:

npx resend-mcp
**Step 2 — Configure Claude Code:**

Add the following to your `.claude/mcp.json` file (create it at the root of your project if it does not exist):

```json
{
  "mcpServers": {
    "resend": {
      "command": "npx",
      "args": ["resend-mcp"],
      "env": {
        "RESEND_API_KEY": "your_api_key_here"
      }
    }
  }
}

Replace your_api_key_here with your actual Resend API key. Do not commit this file to version control — add .claude/mcp.json to your .gitignore.

Step 3 — Restart Claude Code and confirm the resend server appears in your active MCP connections.

Works Best With

Resend MCP Server is documented as compatible with Claude Code. If you use Claude Desktop, the same JSON config structure applies but the config file path is claude_desktop_config.json (location varies by OS — check Anthropic’s Claude Desktop documentation for the exact path). Compatibility with other MCP clients (Cursor, Windsurf, etc.) is not officially documented for this server; behavior may vary.

Known Limitations

• API key required: The server will not function without a valid RESEND_API_KEY set in the environment. There is no fallback or anonymous mode.
• Resend plan limits apply: All sends are subject to your Resend account’s rate limits and monthly sending quotas. The MCP server does not add its own throttling layer — hitting Resend’s limits will surface as API errors in Claude.
• Domain verification: Sending from custom domains requires those domains to be verified inside your Resend account beforehand. The MCP server cannot initiate or complete domain verification.
• No inbound email: This server handles outbound email only. Receiving, parsing, or replying to inbound messages is outside its scope.
• Secrets exposure risk: Passing API keys via env in config files is convenient but carry real risk if files are accidentally committed or shared. Use environment variable injection or a secrets manager in team environments.

Community Resources

• GitHub Issues — resend/resend-mcp — bug reports, feature requests, and setup questions
• Resend GitHub Discussions — broader Resend API questions that may relate to MCP usage
• r/ClaudeAI on Reddit — search “Resend MCP” for community integration threads