Resend

Send and manage email through Resend from your agent.

Transport: Remote HTTP + local stdio
Status: Official · Resend
Auth method: OAuth (remote) or Resend API key (Bearer header / RESEND_API_KEY)RESEND_API_KEY
Scopes / permissions: Not documented
Last verified: Oct 16, 2026
Tools listed: 02

§1What it does

Resend's MCP server lets agents send emails and work with the Resend API. Use the hosted server or run it locally with a Resend API key.

Remote server (OAuth)

{
  "mcpServers": {
    "resend": {
      "url": "https://mcp.resend.com/mcp"
    }
  }
}

Claude Code (remote, OAuth)

claude mcp add --transport http resend https://mcp.resend.com/mcp
# then run /mcp and select resend to log in

Claude Code (remote, API key)

claude mcp add --transport http resend https://mcp.resend.com/mcp --header "Authorization: Bearer re_xxxxxxxxx"

Claude Code (local)

claude mcp add resend -e RESEND_API_KEY=re_xxxxxxxxx -- npx -y resend-mcp

Snippets adapted from the official documentation. Check the official page for current options and auth requirements.

Removed locallyClear the sign-in or remove the server in your MCP client (for example claude mcp logout or claude mcp remove in Claude Code, or log out of the server in Cursor). This only deletes the client's copy of the tokens.
Authorization revokedFind Resend's connected-apps / authorized applications page and revoke the grant there. We haven't found an official page for it yet. This is what stops the refresh token; clearing the client alone is not enough.

Why both steps: OAuth token refresh in the security checklist.