Matrix / Email Sending / Resend

Resend MCP server

Email Sending · remote · Up · auth · Docs + endpoint checked 2026-10-16

Resend has an official hosted MCP server at https://mcp.resend.com/mcp. It uses OAuth (browser login and approval); Resend API key as Bearer token for headless clients over Streamable HTTP (also local stdio or HTTP via npx resend-mcp). Agents can use: emails (send, batch, schedule, cancel), received emails, inboxes (beta, remote only). Last checked 2026-10-16 10:06 PT: Up · auth.

Works in: ClaudeClaude CodeCursorCopilot
Sources: Claude · Claude Code · Cursor · Copilot, checked 2026-10-16
Access: Read + write
Credits: Credits not confirmed
Plan: Not confirmed
Setup: Self-serve
No admin step in the vendor's setup notes. Source: resend.com, checked 2026-10-16
Useful for: Marketing, SDRs, RevOps

Resend MCP endpoint and transport

https://mcp.resend.com/mcp

Transport: Streamable HTTP (also local stdio or HTTP via npx resend-mcp)
Docs: Official Resend MCP docs

Connect Resend without code

Resend's docs confirm it works in Claude. You don't need a terminal or a config file. Check Resend's docs first: some vendors give you a personal URL or an API key to use in place of the plain endpoint.

Claude (web and desktop app)

If Resend shows up when you browse connectors in Claude, connect it from there instead. That skips steps 2 to 4.

In Claude, open Customize → Connectors.
Click + Add, then Add custom connector.
Name it “Resend”, paste the server URL https://mcp.resend.com/mcp, and click Continue.
Review the sign-in settings Claude detected and click Add.
Click Connect and sign in to Resend. Then ask Claude something like “What can the Resend connector do?”

On Team and Enterprise plans, an Owner adds the connector first under Organization settings → Connectors → Add → Custom → Web. Each person then connects it from Customize → Connectors. Free plans can add one custom connector.

Steps from the Claude Help Center: support.claude.com, checked 2026-10-16

From Resend's docs: Claude has a one-click connector in the directory (installs MCP server plus Resend skills) or Add custom connector; Claude Code via the official plugin then /mcp OAuth login; Copilot via VS Code settings.json. Headless clients pass a Resend API key as a Bearer token.Source: resend.com, checked 2026-10-16

Developer setup (Claude Code, Cursor)

Add this to .mcp.json (Claude Code, project root) or ~/.cursor/mcp.json (Cursor). Remove the // comment line if your client requires strict JSON.

{
  "mcpServers": {
    "resend": {
      "url": "https://mcp.resend.com/mcp"
      // headless alternative: "headers": { "Authorization": "Bearer YOUR_RESEND_API_KEY" }
    }
  }
}

Add the endpoint to your client config (above), or as a custom connector in Claude.
Complete the OAuth sign-in. In Claude Code, run /mcp and pick the server.
Test it with a prompt like: “List the tools the Resend MCP server exposes.”

Resend MCP authentication

OAuth (browser login and approval); Resend API key as Bearer token for headless clients

What it can change

Read + write Some Resend MCP tools change data, not just read it.

Things it can do in your Resend account:

sends, batch-sends, schedules, updates and cancels emails
creates, sends and updates broadcast campaigns
creates, updates and removes contacts and imports CSVs
creates and updates templates and automations
creates, verifies and removes sending domains
creates and removes API keys and webhooks
replies to, forwards and drafts inbox emails (beta)

Source: resend.com, checked 2026-10-16

Review each change before you approve it, especially anything that sends messages or edits records other people rely on.

Cost and credits

Not confirmed Resend's docs don't say whether MCP calls use credits or paid usage.

Plan required

Not confirmed Resend's docs don't name a minimum plan for the MCP server.

Admin and governance

Controls Resend itself provides. Settings inside Claude or ChatGPT aren't counted here.

An admin must approve or enable the connectionNot confirmed
Scopes or permissions can limit what it reachesNot confirmed
Individual tools can be turned offNot confirmed
MCP activity shows in an audit logNot confirmed

What the Resend MCP server can do

emails (send, batch, schedule, cancel)
received emails
inboxes (beta, remote only)
templates
contacts
broadcasts
automations
events
domains
segments & topics
API keys
webhooks
logs

Resend MCP status

Up · auth HTTP 401 · 132 ms · checked 2026-10-16 10:06 PT. Full status and history.

Resend MCP FAQ

What is the Resend MCP server URL?

https://mcp.resend.com/mcp

How does Resend MCP authenticate?

OAuth (browser login and approval); Resend API key as Bearer token for headless clients.

Which apps does Resend MCP work with?

Resend's docs confirm it works in Claude, Claude Code, Cursor and GitHub Copilot. Other apps aren't confirmed in the docs yet.

Can I use Resend in Claude without code?

Yes. Resend's docs confirm it works in Claude. Add it as a connector in the app settings and sign in. No terminal or config file needed.

Can the Resend MCP server change my data?

Yes. Some tools change data, for example: sends, batch-sends, schedules, updates and cancels emails, creates, sends and updates broadcast campaigns, creates, updates and removes contacts and imports CSVs. Review each change before you approve it.

Is the Resend MCP server official?

Yes. It's documented on resend.com, last checked 2026-10-16.

Related MCP servers

Artisan (Cold Email & Outreach)
Evaboot (LinkedIn Automation & Scraping)
HeyReach (LinkedIn Automation & Scraping)
Instantly (Cold Email & Outreach)
lemlist (Cold Email & Outreach)

Something out of date on this page? Report a correction, with a link to the vendor page that shows the right information.