resend-mcp
Provides an MCP server for the Resend email platform, enabling MCP clients to send/receive and manage related email resources (contacts, broadcasts, domains, segments, topics, API keys, and webhooks) via stdio (default) or HTTP transport.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTP mode uses Bearer token with the Resend API key supplied by the MCP client; this increases risk if the endpoint is exposed or logs capture headers. README does not mention TLS requirements, safe logging practices, or rate-limit/security error guidance. The project depends on common libraries (express, zod, resend, MCP SDK), but dependency freshness/CVE status is not provided here.
⚡ Reliability
Best When
You want to integrate Resend capabilities into an AI agent workflow through MCP (Claude Desktop/Cursor/Claude Code), either locally over stdio or via HTTP.
Avoid When
You need fine-grained organizational access controls beyond what a single Resend API key can provide, or you want to avoid passing credentials to an HTTP MCP endpoint.
Use Cases
- • Send transactional or marketing emails from an MCP client
- • Inspect inbound/received emails and download attachments
- • Manage contact lists, segments, and topic subscriptions
- • Create and manage broadcast campaigns with scheduling/personalization
- • Configure and verify sender domains
- • Programmatically manage Resend API keys and webhook configurations
Not For
- • Use when you need OAuth/SSO-based delegation instead of API-key/Bearer-token authentication
- • Use when you require an OpenAPI/REST SDK interface directly (this is MCP-focused)
- • Use when you cannot verify domain ownership or need to send to unverified recipients outside your domain rules
Interface
Authentication
Authentication is based on a Resend API key. In HTTP mode, the client supplies the API key as a Bearer token per request/connection configuration.
Pricing
Pricing is not described in the provided README; Resend typically charges per email operations, but this package’s pricing details are not stated here.
Agent Metadata
Known Gotchas
- ⚠ HTTP transport requires clients to pass Authorization: Bearer <Resend API key>; ensure you don’t expose the key or send it to untrusted environments.
- ⚠ If SENDER_EMAIL_ADDRESS is not provided, the server may prompt/ask for a sender on each call (per README note), which can disrupt fully automated flows.
- ⚠ Idempotency behavior for send/cancel/update operations is not documented in the README; agents may need to avoid automatic retries without confirmation.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for resend-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.