Resend MCP connector
Connect Resend to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
List Resend broadcasts sent to the Product Updates audience
Working in Resend with Elaichi
-
List all Resend API keys
-
Get single Resend broadcast by ID
-
List all Resend broadcasts
How to connect Resend to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Resend MCP connector for 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.
Resend MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Resend MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Resend MCP connector for 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.
Resend MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Resend through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Resend is logged.
-
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”
What connecting Resend gets you
6 screens from Elaichi, each doing one job for your Resend account.
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, Cursor or Microsoft Copilot
The agent
Ask about broadcasts, get real answers.
Plain language questions answered from live Resend broadcasts, contacts and audiences.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Resend.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
77 Resend tools, zero custom code.
Broadcasts, contacts, contact properties, segments and API keys, all callable today.
Toolboxes
Each team gets its own toolbox.
Lifecycle sends broadcasts, support reads contacts, scoped per team inside Resend.
Shared connections
Teammates send without seeing a key.
Every Resend connection shows who added it and which teams share it.
Audit log
Every Resend call is on record.
When, who, what happened, type and resource for each broadcast and contact.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Resend digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Resend
Queued
Automations
A schedule drafts your weekly digest.
Resend broadcasts fetched, grouped, drafted by an agent, approved, then posted back.
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%
Collections and dashboards
Resend email health, counted not guessed.
Four metrics, 14 days of contacts created, split by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Resend
All three can connect Resend to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Resend tools | Allow or restrict single Resend tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Resend call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting specific actions for a role, 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 restricting deletes, or restricting the creation of API keys and domains. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client at the same time.
Does the Resend MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Resend is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Resend?
Yes. Both let Claude, ChatGPT or Cursor use Resend. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Resend call.
How is Elaichi different from Composio for Resend?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Resend: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Resend in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot