Access, auth, and limits
The hosted server takes auth two ways, and this is the part worth knowing. OAuth 2.0 covers clients that can open a browser, and a Resend API key sent as a Bearer token covers headless environments that cannot. That means one endpoint serves both your desktop assistant and a CI job, with no separate deployment for either. The self-hosted build takes an API key through the environment.
If you configured this earlier from a directory listing, check the URL. resend.com/mcp is the marketing page and returns HTML; the endpoint is mcp.resend.com/mcp. The /.well-known/mcp.json file is the authoritative source for the endpoint, transport and OAuth configuration, and is worth reading directly rather than trusting a third-party listing.
Where it works and what to build
Any MCP client that speaks streamable HTTP and OAuth connects without special handling, and the self-hosted stdio build covers clients that cannot do the browser handshake. Resend documents Cursor and Claude explicitly.
The workflow this suits is incident response rather than routine sending. When a broadcast underperforms, an agent can pull the send stats, check whether the domain's authentication records still verify, inspect which segment actually received it and read recent webhook deliveries for bounces, all without you opening four dashboard tabs. Sending itself is usually better left to your application code; the value here is the diagnostic surface around it.
Which AI clients can use Resend MCP?
Not every AI assistant supports MCP natively. Per-client picture for Resend:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | — |
| Claude Code | Native MCP | — |
| Cursor | Native MCP | — |
| Codex | Native MCP | — |
| Windsurf | Native MCP | — |
| Gemini | Native MCP | — |
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": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.resend.com/mcp
// Claude Code (one-liner): claude mcp add resend <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.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.
- 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
Textbook execution: hosted and self-hosted, OAuth on the hosted path, and a well-known discovery document that makes the whole thing introspectable. If you want a model for how to ship an MCP server, this is it.
Strong agent-fit for Claude workflows. Resend includes an official MCP server and comprehensive API coverage with OpenAPI spec plus SDKs across 6 languages, making it straightforward to integrate into agentic email tasks. The main gap is lack of webhook support, which limits real-time event handling in multi-step workflows.
Scored 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://mcp.resend.com/mcp
- API docs: https://resend.com/docs/mcp-server
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.