Skip to content

Email

Resend MCP connector

Connect Resend to Elaichi and Claude, ChatGPT, Cursor, or any MCP client can create and update broadcasts, manage contacts, segments and topics, and handle API keys and domains as the person who signed in.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Resend to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Resend once

  1. Open Connections, choose Add connection, and pick Resend.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Resend API key. One person generates a token in Resend and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

resend
Resend
Amply
Gmail
Mailchimp
Mailtrap
Outlook Mail
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Resend to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Resend to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Resend to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Resend to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Resend through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Marketing

    Draft the launch broadcast before it sends

    Ask for a new Resend broadcast with the announcement copy, then have the subject line, preview text, and audience adjusted in plain language. Review the draft in Resend before anything goes out.

  • Growth

    Build a segment for the next campaign

    Describe who you want to reach, such as trial users who signed up this month, and get a Resend contact segment created and ready to pick when the broadcast is set up.

  • Support

    Fix a contact's details after a ticket

    Look up a Resend contact by email, correct a misspelled name, or mark them unsubscribed when they ask to stop hearing from you, without leaving the conversation with the customer.

  • Product

    Track plan tier on every contact

    Add a new contact property to Resend, such as plan or signup source, so future segments and broadcasts can be aimed at the right people.

  • Engineering

    Rotate an API key and add a domain

    List the Resend API keys in use, create a fresh one for a new service, and remove the old one. Register a new sending domain when a product gets its own address.

  • Operations

    Tidy up topics and preferences

    See every Resend contact topic your audience can opt in or out of, rename the ones that no longer match how you describe your emails, and keep the preference center current.

Try asking

  • “List Resend broadcasts sent to the Product Updates audience”
  • “Which contact properties are missing on our newsletter segment?”
  • “Draft a broadcast for contacts in the EMEA segment”

See all 77 Resend tools below

AI tools

Resend tools for your AI agents

77 tools are ready to call through Elaichi's MCP endpoint the moment you connect Resend, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Resend gets you

6 screens from the product, each doing one job for your Resend account.

The agent

Ask about broadcasts, get real answers.

Plain language questions answered from live Resend broadcasts, contacts and audiences.

  • broadcasts
  • contacts
  • segments
  • api keys

Ask Elaichi to work across your apps.

List Resend broadcasts sent to the Product Updates audience

Which contact properties are missing on our newsletter segment?

Draft a broadcast for contacts in the EMEA segment

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Resend.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

77 Resend tools, zero custom code.

Broadcasts, contacts, contact properties, segments and API keys, all callable today.

  • Create a Resend API key
  • Delete a Resend API key by ID
  • List all Resend API keys
  • Create a Resend broadcast
ElaichiTools
Tool Action Description
Create a Resend API key Create Create a new API key in Resend. Returns id and token — the plaintext token is only included in this response and cannot be retrieved later, so store it immediately. Required: name.
Delete a Resend API key by ID Delete Permanently delete a Resend API key by id. Returns an empty 200 response on success. Required: id.
List all Resend API keys List List all API keys for the authenticated Resend team. Returns: id, name, created_at, last_used_at for each key.
Create a Resend broadcast Create Create a new broadcast in Resend. Returns the id of the created broadcast. Required: from, subject. Created as a draft by default; set send: true to send immediately, or combine send: true with scheduled_at to schedule delivery for a later time.
Delete a Resend broadcast by ID Delete Delete a Resend broadcast by id. Only broadcasts in draft status can be deleted; deleting a scheduled broadcast also cancels its pending delivery. Returns: object, id, deleted.

Toolboxes

Each team gets its own toolbox.

Lifecycle sends broadcasts, support reads contacts, scoped per team inside Resend.

  • Lifecycle marketing
  • Growth
  • Support
  • Engineering
ElaichiToolboxes
Name Source template Tools Created

Lifecycle marketing toolbox

Resend · broadcasts and audiences

Resend starter 18 Mar 4, 2026

Growth toolbox

Resend · segments and contact properties

9 Mar 2, 2026

Support toolbox

Resend · contact lookups

24 Feb 27, 2026

Engineering toolbox

Resend · api keys and transactional sends

Resend starter 6 Feb 19, 2026

Product toolbox

Resend · release announcement broadcasts

31 Jan 30, 2026

Compliance toolbox

Resend · unsubscribes and contact records

12 Jan 22, 2026

Shared connections

Teammates send without seeing a key.

Every Resend connection shows who added it and which teams share it.

  • Lifecycle
  • Growth EMEA
  • Support
  • Product updates
ElaichiConnections
Connection Scope Status Access
RE

Resend (Lifecycle)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
RE

Resend (Growth EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
RE

Resend (Support)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
RE

Resend (Product updates)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
RE

Resend (Engineering)

Connected by Clara Nowak

Personal • Active Not shared
RE

Resend (Newsletter)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Resend call is on record.

When, who, what happened, type and resource for each broadcast and contact.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Resend Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Resend Broadcasts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Resend Broadcasts List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule drafts your weekly digest.

Resend broadcasts fetched, grouped, drafted by an agent, approved, then posted back.

Resend digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch broadcasts

    Resend

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Resend

    Queued

Collections and dashboards

Resend email health, counted not guessed.

Four metrics, 14 days of contacts created, split by team, refreshed on schedule.

Resend health

Refreshed 4 minutes ago · every 15 minutes · from the broadcasts collection

Live

Broadcasts

1,284 ↓ 12%

Contacts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Broadcasts created

Last 14 days

By team

Share of activity

Lifecycle 34%

Growth EMEA 27%

Support 21%

Product updates 18%

FAQ

Frequently asked questions

How do I connect Resend to Claude?

First, connect Resend inside Elaichi by pasting a Resend API key when prompted. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Resend is available in the conversation.

Does Resend work with ChatGPT and Cursor as well as Claude?

Yes. Once Resend is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Resend once and every client you use picks it up.

What can an AI agent actually do with my Resend data?

With Resend connected, an agent can draft, update, or remove broadcasts, add and edit contacts, build segments, manage the topics people subscribe to, and add contact properties like plan or region. It can also list, create, and delete Resend API keys and register a new sending domain. Because Resend offers a lot of actions, short concrete asks such as "unsubscribe [email protected]" work better than long multi-part sentences.

Does connecting Resend give the AI access to everything in my account?

An agent working through Elaichi can only do what the Resend API key it was connected with allows, so a key limited to sending or to one domain stays limited. Elaichi can narrow that further by blocking specific actions for a team, but it can never grant more than the key already permits.

Can my team share one Resend connection?

Yes. One person connects Resend in Elaichi with an API key and shares it with a team, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who created a broadcast or changed a contact in Resend.

Can I stop an agent from deleting or changing things in Resend?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Resend contacts and broadcasts while blocking deletes, or blocking the creation of API keys and domains. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt can reach it.

What happens to a Resend connection when someone leaves?

When a person is offboarded in Elaichi, their access to Resend through every connected client ends at once. If they had shared a Resend connection with a team, it keeps working for everyone else. Disconnecting Resend once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

Put Resend in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.