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.
In Elaichi
Connect Resend once
-
Open Connections, choose Add connection, and pick Resend.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
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
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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”
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.
No tools match your search.
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.
Copy the endpoint
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
Toolboxes
Each team gets its own toolbox.
Lifecycle sends broadcasts, support reads contacts, scoped per team inside Resend.
- Lifecycle marketing
- Growth
- Support
- Engineering
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
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
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
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch broadcasts
Resend
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
Related connectors
More from the catalog
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 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.