Available

Resend MCP server

Resend is a developer-focused email API for sending transactional and marketing email, managing domains, audiences, contacts, and templates. Connect through Arc0 to use the actions your identity is allowed to call.

EmailAPI keyMCP + RESTresend.com
AUDIT LOG · RESENDPOLICY: acme-support
09:41:07 · claude · u_8f2read
resend.list_emails
List sent emails✓ allowed · 212ms
09:41:08 · claude · u_8f2read
resend.get_email
Get a sent email✓ allowed · 164ms
09:41:09 · claude · u_8f2write
resend.create_contact
Create a contact✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
resend.cancel_scheduled_email
Cancel a scheduled email✕ blocked · policy: deny
ILLUSTRATIVE POLICY TRACE · NOT A LIVE RECEIPT
01 · USE CASES

Agent workflows for Resend.

01

Send an email

Send or schedule a real email from a verified Resend domain (up to 10 to, 5 cc, 5 bcc). Use when the user explicitly asks to send. Each recipient counts as one email of plan quota or paid usage; a timed-out send may still deliver and count, so check list_emails before sending again.

02

Get a sent email

Get one email sent through Resend: recipients, subject, delivery status (last event such as delivered, bounced or scheduled) and its text/HTML body clipped to maxChars. Use when the user asks whether an email was delivered or what it said.

03

List sent emails

List emails the Resend team sent or scheduled, newest first, with recipients, subject and delivery status. Use when the user asks what was sent recently or needs an email id; pass nextCursor as cursor for more.

02 · ACTIONS

10 Resend actions, graded by risk.

These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.

read

7

Look things up, subject to your permissions.

  • resend.get_email
    Get a sent email

    Get one email sent through Resend: recipients, subject, delivery status (last event such as delivered, bounced or scheduled) and its text/HTML body clipped to maxChars. Use when the user asks whether an email was delivered or what it said.

  • resend.list_emails
    List sent emails

    List emails the Resend team sent or scheduled, newest first, with recipients, subject and delivery status. Use when the user asks what was sent recently or needs an email id; pass nextCursor as cursor for more.

  • resend.list_domains
    List domains

    List the Resend team domains with verification status, region and whether sending or receiving is enabled. Use when choosing a from address or checking which domains are verified; use get_domain for DNS records.

  • resend.get_domain
    Get a domain and its DNS records

    Get one Resend domain with its verification status and the DNS records (SPF, DKIM, MX, tracking) with each record status. Use when the user needs to set up or debug DNS for a sending domain.

  • resend.list_segments
    List segments

    List the Resend team contact segments (formerly called audiences) with their ids. Use when the user asks which segments or audiences exist, or needs a segment id to list contacts or add a new contact to it.

  • resend.list_contacts
    List contacts

    List Resend contacts (marketing recipients), optionally only those in one segment, with name and subscription status. Use when the user asks who is on a list or segment; pass nextCursor as cursor for more.

  • resend.get_contact
    Get a contact

    Get one Resend contact by id or email address, with name, subscription status and custom properties. Use when the user asks about a specific contact or whether someone is already a contact.

write

2

Create and change things. Allow, or ask the user first.

  • resend.send_email
    Send an email

    Send or schedule a real email from a verified Resend domain (up to 10 to, 5 cc, 5 bcc). Use when the user explicitly asks to send. Each recipient counts as one email of plan quota or paid usage; a timed-out send may still deliver and count, so check list_emails before sending again.

  • resend.create_contact
    Create a contact

    Create a Resend contact for an email address, optionally in up to 10 segments. Use when the user asks to add someone to their contacts or a segment. Does not call the sending endpoint, but configured automations may react. If the outcome is unknown, check get_contact before retrying.

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • resend.cancel_scheduled_email
    Cancel a scheduled email

    Cancel a Resend email that is still scheduled so it is never sent. Use when the user asks to stop or call off a scheduled email. Final: a canceled email cannot be rescheduled; send a new one instead.

03 · POLICIES AND AUDIT

Control access to Resend.

Connect the intended Resend account, authorize your AI client and set policies for its tools.

Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.

Configure policies and approvals

Example policy choices

  • Read actions: allow where authorized
  • resend.create_contact: require approval
  • resend.cancel_scheduled_email: deny

Arc0 MCP endpoint: https://api.arc0.ai/mcp

04 · AUTH AND DATA

How Resend connects.

Connect Resend using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · AI CLIENTS

Use Resend with your AI client.

Sign in to Arc0 and connect Resend in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.

Resend with Claude

Claude Desktop + Claude Code

  1. In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
  2. For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
  3. Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Claude
Resend with ChatGPT

ChatGPT on the web

  1. Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
  2. Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
  3. Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for ChatGPT
Resend with OpenAI Codex

Codex app + CLI

  1. Run the registration command below. The app and CLI share ~/.codex/config.toml.
  2. Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
  3. Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for OpenAI Codex
Resend with Cursor

Remote MCP setup

  1. Add Arc0 in your client’s remote MCP settings using the server URL below.
  2. Choose OAuth, sign in to Arc0, select the intended workspace and review access.
  3. Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
All apps for Cursor
Resend with VS Code

Remote MCP setup

  1. Add a remote HTTP MCP server named Arc0 using the URL below.
  2. Use OAuth and finish Arc0 sign-in, workspace selection and consent.
  3. Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting
Resend with Any MCP client

Streamable HTTP

  1. Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
  2. For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
  3. Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcp
Full MCP setup and troubleshooting

After setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.

07 · FAQ

Resend and Arc0, answered.

Q01

Does Resend work with Claude Desktop and Claude Code?

Yes, after connecting the account and authorizing the client. Use Arc0’s remote MCP endpoint with OAuth. Claude Code has a documented registration command; Desktop uses the generic remote-client setup.

Q02

Can I use Resend with OpenAI Codex, ChatGPT and Cursor?

Yes, after connecting the account and authorizing the client. Codex and ChatGPT have setup instructions in Arc0’s MCP clients guide. Cursor uses the generic remote-MCP steps. Tool access remains scoped to the authorized identity.

Q03

Is this the official Resend MCP server?

This is Arc0’s integration page, not a claim of an official Resend server. Arc0 adds a shared connection, policy and audit experience across apps. Consult Resend for its own current MCP offerings.

Q04

Which Resend actions are supported?

10 registry-defined actions: 7 read, 2 write and 1 destructive. Provider permissions, access enablement and Arc0 policy determine what can execute.

Q05

Which permissions does Resend need?

Connect Resend using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.

Q06

Can I restrict writes in Resend?

You can deny write and destructive actions or require approval. Provider scopes and Arc0 action policies are separate controls; a policy does not grant additional provider permissions.

Q07

What does Resend through Arc0 cost?

See Arc0 pricing for current connectivity plans. The provider may require its own subscription or charge per request. Arc0 plan allowances do not make third-party data or paid actions free.

Get started

Plug Resend into your agent.

Resend MCP server: 10 actions including send an email, get a sent email, list sent emails. Connect through Arc0.

Free to build · MCP + REST · Audit log on every plan

Resend and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Resend.