How to connect Resend MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"resend": {
"command": "npx",
"args": ["-y", "<server-package-name>"],
"env": {
"RESEND_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://resend.com/mcp
// Check the server's README for the exact "command" and required env vars.Some MCP servers require an API key. Check the source page for setup: resend.com/mcp.
Does Resend MCP cost extra?
Resend ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Resend plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
Resend also publishes a REST API
Resend publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Resend from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What campaigns underperformed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Resend data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Resend account
- Multi-account workflows without context-switching the Resend UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Resend data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Resend safe
Limits and gotchas
- Official MCP server — published by Resend themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Auth flow: MCP servers usually inherit the underlying API auth method (both). Expect to configure that on first install.
- OpenAPI spec is published — easy to validate which endpoints the MCP server actually exposes vs the full API surface.
- Rate limits: MCP calls count against your underlying Resend API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Strong agent-fit for Claude and Cursor workflows. Resend offers an official MCP server, OpenAPI spec, and SDKs across 6 languages (Node, Python, Go, Ruby, PHP, Java), making it straightforward to integrate into agentic email tasks. The main gap is lack of webhook support, which limits real-time event-driven automation patterns.
Scored 2026-05-21 by Joonas (TMB).
Resend MCP & API FAQ
Is the Resend MCP server official?+
Can I use the Resend MCP with Cursor or Codex?+
Does Resend have a public API?+
Does Resend publish an OpenAPI / Swagger spec?+
Sources
- Resend official site: https://resend.com
- MCP server page: https://resend.com/mcp
- API docs: https://resend.com/docs/introduction
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

