How to connect Resend MCP to Claude

Connect Claude Web, Desktop and Cowork to Resend MCP. Send transactional receipt email to customer, resend failed emails to recipients now, and more using natural language, with authentication handled for you.

Resend MCP logoResend MCP
Dcr Oauth

Resend MCP is a transactional email service for sending and managing programmatic email. It provides fast, developer-friendly APIs and templates for reliable delivery.

95 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Resend account to Claude via Composio Connect, enabling it to send transactional receipt email to customer, resend failed emails to recipients now, preview email template with test recipients, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Resend MCP with

Connecting Resend to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Resend account

Back in Claude, ask it to connect to Resend or give it any Resend-related task.

For example, ask Claude to:

  • "Send transactional receipt email to customer"
  • "Resend failed emails to recipients now"
  • "Preview email template with test recipients"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Resend account is ready to use.

What is the Resend Claude Connector, and what's possible with it?

The Resend MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Resend account. It provides structured and secure access so your agent can perform Resend operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for Resend?

The connector can show as connected, but Claude must use it in each Resend conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Resend again.

2. Why does Claude show an MCP server error before Resend connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Resend.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Resend.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Resend authorization link not work?

The Composio connector is one server. Your Resend account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Resend connection.
  • Composio creates a fresh Resend authorization link.
  • Open that link in your browser and finish the Resend sign-in.

4. Why do Resend actions fail after they worked before?

The Resend connection can expire or lose permission.

  • Ask Claude to inspect the Resend connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Resend account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Resend.
  • If the action still fails with a permission error, check that the connected account has that permission in Resend itself.

5. How do I switch to a different Resend account?

Claude can manage the Resend connection for you.

  • Ask Claude to disconnect or delete the current Resend account.
  • Ask Claude to connect Resend again.
  • Open the new Composio authorization link for Resend.
  • Sign in with the other Resend account in the browser.
  • After the account connects, ask Claude to retry the Resend task.

6. Why is my Resend connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Resend connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Resend tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Resend.
TOOLS

Supported Tools

Every Resend MCP action and event your agent gets out of the box.

Add-contact-to-segment

Add a contact to a segment in Resend (by contact ID or email).

Add-suppression

Add an email address to the suppression list in Resend.

Batch-add-suppressions

Add multiple email addresses to the suppression list in Resend in a single call.

Batch-remove-suppressions

Remove multiple entries from the suppression list in Resend in a single call, by email addresses or by suppression IDs (provide exactly one of the two).

Cancel-broadcast

**Purpose:** Cancel a queued or scheduled broadcast by ID or Resend dashboard URL, without removing it.

Cancel-email

Cancel a scheduled email that has not yet been sent.

Compose-broadcast

**Purpose:** Set the TipTap JSON content of a broadcast, enabling it to be edited visually in the Resend dashboard editor.

Compose-template

**Purpose:** Set the TipTap JSON content of a template, enabling it to be edited visually in the Resend dashboard editor.

Connect-to-editor

**Purpose:** Show agent presence in the Resend dashboard editor.

Create-api-key

Create a new API key in Resend.

Create-automation

**Purpose:** Create an automation workflow that triggers on events and executes a sequence of steps.

Create-broadcast

**Purpose:** Create a broadcast campaign (one email sent to an entire segment).

Create-contact

Create a new contact in Resend.

Create-contact-import

Bulk-import contacts from a CSV file into Resend.

Create-contact-property

Create a new contact property in Resend.

Create-domain

Create a new domain in Resend.

Create-domain-claim

Start a claim for a domain another Resend account has already verified.

Create-segment

Create a new segment in Resend.

Create-template

Create a new email template in Resend.

Create-topic

Create a new topic in Resend.

Create-webhook

Create a new webhook in Resend.

Disconnect-from-editor

Remove agent presence from the Resend dashboard editor.

Duplicate-automation

Duplicate an existing automation by ID or Resend dashboard URL.

Duplicate-template

Duplicate an existing email template in Resend.

Get-automation

**Purpose:** Get details of a specific automation (with its workflow) or list all automations.

Get-automation-runs

**Purpose:** List runs for an automation, or get details of a specific run.

Get-broadcast

Retrieve full details of a specific broadcast by ID or Resend dashboard URL (e.

Get-contact

Get a contact by ID or email from Resend.

Get-contact-import

Get the status and counts of a contact import by ID.

Get-contact-property

Get a contact property by ID from Resend.

Get-domain

Get a domain by ID from Resend.

Get-domain-claim

Retrieve the latest claim for a domain by its placeholder Domain ID (the domain_id from create-domain-claim).

Get-email

Retrieve full details of a specific sent transactional email by ID, including message_id, HTML and plain text content.

Get-log

**Purpose:** Get detailed information about a specific API request log, including the full request and response bodies.

Get-received-email

Retrieve full details of a specific received email by ID, including HTML and plain text content, headers, and raw email download URL.

Get-received-email-attachment

Retrieve details of a specific attachment from a received email, including a time-limited download URL.

Get-segment

Get a segment by ID from Resend.

Get-sent-email-attachment

Retrieve details of a specific attachment from a sent email, including a time-limited download URL.

Get-suppression

Get a suppression list entry by ID or email address from Resend.

Get-template

Get an email template by ID, alias, or Resend dashboard URL (e.

Get-tiptap-json-content

**Purpose:** Retrieve the existing TipTap JSON content of a broadcast or template, optionally bundled with the TipTap schema reference.

Get-topic

Get a topic by ID from Resend.

Get-webhook

Get a webhook by ID from Resend.

List-api-keys

List all API keys from Resend.

List-broadcasts

**Purpose:** List all broadcast campaigns (newsletters/bulk emails to audiences) with ID, name, audience, status, timestamps.

List-contact-imports

List contact imports from Resend.

List-contact-properties

List all contact properties from Resend.

List-contacts

**Purpose:** List contacts from Resend.

List-contact-segments

List all segments a contact belongs to in Resend (by contact ID or email).

List-contact-topics

List all topic subscriptions for a contact in Resend (by contact ID or email).

List-domains

List all domains from Resend.

List-emails

**Purpose:** List recently sent emails (transactional emails sent via send-email) with metadata: recipient, subject, status, timestamps.

List-logs

**Purpose:** List API request logs for the account.

List-oauth-grants

List OAuth grants for the team — the apps authorized to act on the team's behalf.

List-received-email-attachments

List all attachments from a specific received (inbox) email.

List-received-emails

**Purpose:** List emails received (inbox) by your Resend receiving address.

List-segments

**Purpose:** List all segments in the account.

List-sent-email-attachments

List all attachments from a specific sent email (from send-email or list-emails).

List-suppressions

**Purpose:** List email addresses on the suppression list.

List-templates

List all email templates from Resend.

List-topics

List all topics from Resend.

List-webhooks

List all webhooks from Resend.

Manage-events

**Purpose:** Create, list, get, update, or remove event definitions in Resend.

Publish-template

Publish an email template in Resend.

Remove-api-key

Remove an API key by ID from Resend.

Remove-automation

Remove an automation by ID or Resend dashboard URL.

Remove-broadcast

Remove a broadcast by ID or Resend dashboard URL.

Remove-contact

Remove a contact from Resend (by ID or email).

Remove-contact-from-segment

Remove a contact from a segment in Resend (by contact ID or email).

Remove-contact-property

Remove a contact property by ID from Resend.

Remove-domain

Remove a domain by ID from Resend.

Remove-segment

Remove a segment by ID from Resend.

Remove-suppression

Remove an entry by ID or email address from the suppression list in Resend, allowing the address to receive emails again.

Remove-template

Remove an email template by ID, alias, or Resend dashboard URL from Resend.

Remove-topic

Remove a topic by ID from Resend.

Remove-webhook

Remove a webhook by ID from Resend.

Revoke-oauth-grant

Revoke an OAuth grant by ID.

Send-batch-emails

**Purpose:** Send up to 100 transactional emails in one API call.

Send-broadcast

**Purpose:** Send (or schedule) an existing broadcast by ID.

Send-email

**Purpose:** Send a single transactional email to one or more recipients immediately (or schedule it).

Send-event

**Purpose:** Fire an event to trigger automations for a specific contact.

Share-email

Create a shareable link for a sent or received email, so anyone with the link can view it without Resend dashboard access.

Update-api-key

Rename an existing API key in Resend.

Update-automation

**Purpose:** Update an automation's name, status, or workflow.

Update-broadcast

Update broadcast metadata by ID or Resend dashboard URL (name, subject, from, html, text, segment, preview text, reply-to).

Update-contact

Update a contact in Resend (by ID or email).

Update-contact-property

Update an existing contact property in Resend.

Update-contact-topics

Update topic subscriptions for a contact in Resend (by contact ID or email).

Update-domain

Update an existing domain in Resend.

Update-email

Reschedule a scheduled email by updating its scheduled send time.

Update-template

Update template metadata by ID, alias, or Resend dashboard URL (name, subject, from, html, variables, etc.

Update-topic

Update an existing topic in Resend.

Update-webhook

Update an existing webhook in Resend.

Verify-domain

Trigger domain verification in Resend.

Verify-domain-claim

Trigger asynchronous DNS verification and ownership transfer for a domain claim, using the placeholder Domain ID.

FAQ

Frequently asked questions

With a standalone Resend MCP server, the agents and LLMs can only access a fixed set of Resend tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Resend and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Resend tools.

Yes, absolutely. You can configure which Resend scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Resend data and credentials are handled as safely as possible.

Start with Resend MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Resend MCP tool your agent needs.Free to start.

Start building