Resend
Developer-friendly transactional email.
Verdict
Common use cases
- Send onboarding emails to new signups
- Notify customers of order status changes
- Schedule weekly digest emails from chat
- Cancel mistimed campaign sends before delivery
- Manage contact segments for product launches
Integration
- Vendor
- Resend
- Category
- communication
- Auth
- API_KEY
- Tools
- 18
- Composio slug
resend
Tools
- Cancel Email
Cancel a scheduled email.
- Create Audience
Create a list of contacts.
- Create Contact
Create a contact in resend.
- Create Domain
Create a domain through the resend email api.
- Delete Audiencedestructive
Remove an existing audience.
- Delete Contactdestructive
Delete a contact in resend.
- Delete Domaindestructive
Delete a domain through the resend email api.
- List Audiences
List all audiences.
- List Contacts
List contacts in resend.
- List Domains
List all domains.
- Retrieve Audience
Retrieve a single audience.
- Retrieve Contact
Retrieve a contact in resend.
- Retrieve Domain
Retrieve a single domain.
- Retrieve Email
Retrieve a single email.
- Send Email
Send an email using resend.
- Update Domain
Update an existing domain.
- Update Email
Update a scheduled email.
- Verify Domain
Verify a domain through the resend email api.
Setup
Setup guide
- 11. Log into your Resend dashboard and navigate to API Keys under Settings. 2. Generate a new API key with send and domain management permissions, then copy it. 3. In Switchy, open your workspace settings and click Integrations, then find Resend in the MCP directory. 4. Paste your API key into the authentication field and click Connect. 5. Switchy will verify the key by fetching your domain list — if it succeeds, the integration is live. 6. Open any Space, type '@Resend send an email to alex@example.com with subject Test and body Hello from Switchy', and press send. 7. Check your Resend dashboard logs to confirm the email queued. 8. If the test fails, double-check the API key has send scope and your domain is verified in Resend.
What teammates see: by default, memories from Resend are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Send Welcome Email
@Resend send an email to the user we just discussed with subject 'Welcome to the team' and a friendly introduction body mentioning their role.Open in a Space →
Schedule Reminder
@Resend schedule an email to jordan@company.com for 9am tomorrow with subject 'Sprint planning reminder' and body 'Don't forget our 10am kickoff'.Open in a Space →
Create Contact List
@Resend create an audience named 'Q1 Beta Testers' so we can send targeted updates to early adopters.Open in a Space →
Cancel Scheduled Send
@Resend cancel the scheduled email with ID abc123 that we queued this morning for the product launch.Open in a Space →
Verify Sending Domain
@Resend create a domain for mail.ourcompany.com and show me the DNS records I need to add for verification.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@resend list all audiences and show me the contact count for each one
Based on your Resend account, here are your current audiences: • **Newsletter Subscribers** — 1,247 contacts • **Product Updates** — 892 contacts • **Beta Testers** — 156 contacts • **Customer Onboarding** — 2,104 contacts Each audience maintains its own contact list with independent subscription preferences. The Newsletter Subscribers audience has the highest engagement rate at 34% over the last 30 days.
This example demonstrates read-only audience inspection, useful for understanding your email segmentation before launching campaigns. Requires API key with audiences:read scope. Contact counts reflect the moment of query and may change as subscribers join or leave lists.
@resend create a new contact named Sarah Chen with email sarah.chen@example.com and add her to the Product Updates audience
Contact created successfully: **Sarah Chen** (sarah.chen@example.com) has been added to your Resend account and subscribed to the **Product Updates** audience. The contact ID is `cont_8x7k2m9p` for future reference. Sarah will now receive emails sent to the Product Updates segment. She can unsubscribe at any time via the standard footer link in your transactional emails.
This write operation immediately adds the contact to your account and the specified audience. Before using this in production workflows, ensure you have proper consent from the contact — Resend enforces anti-spam policies and adding contacts without permission can result in account suspension.
@resend I have three scheduled emails queued for tomorrow morning — cancel the one with subject line 'Flash Sale Ending Soon' because we extended the promotion
I've located the scheduled email matching your description: **Subject:** Flash Sale Ending Soon **Scheduled for:** Tomorrow at 9:00 AM EST **Audience:** Newsletter Subscribers (1,247 recipients) This email has been **canceled** and will not be sent. The other two scheduled emails ('Weekly Digest' and 'New Feature Announcement') remain queued for delivery as planned. You can reschedule the flash sale email with updated copy whenever you're ready.
Canceling scheduled emails requires identifying the correct message, typically by subject line or schedule time. This operation is irreversible — once canceled, you'll need to recreate and reschedule the email. The MCP cannot cancel emails already in delivery (status: sending or sent).
Use-case deep-dives
When your support team needs to send receipts or confirmations on the fly
A 3-person support team handling refunds and account changes in Intercom needs to send order confirmations or password-reset emails without leaving the chat window. The Resend MCP lets them trigger transactional sends directly from Switchy—no context-switching to an admin panel. The 18 tools cover the full lifecycle: create contacts, send emails, cancel scheduled sends if a customer changes their mind. This works when your volume is under 500 emails a day and your templates are stable. Above that threshold, you're better off with a dedicated email ops person managing Resend's dashboard. If your support flow already includes sending 5-10 transactional emails per shift, connect this MCP and let your team stay in one workspace.
When a product marketer is building a welcome series without engineering help
A solo product marketer at a 12-person SaaS startup needs to spin up a 5-email onboarding sequence for trial users. The Resend MCP gives them the Create Audience and Create Contact tools to segment users and the domain management tools to verify sending reputation—all from Switchy's shared workspace. They can draft the sequence, schedule sends, and cancel emails if a user converts early, without filing a ticket to engineering. This scenario breaks down if you need complex conditional logic or A/B testing; Resend's API is transactional-first, not a full marketing automation platform. If your onboarding is a linear drip with 3-7 emails and under 200 new trials a week, this MCP gets you live in an afternoon.
When a community manager is sending weekly event invites to segmented lists
A 2-person community team runs 3 recurring events a week—office hours, demo days, user meetups—each with its own invite list. The Resend MCP's List Audiences and Create Contact tools let them manage segmented lists (enterprise users, free-tier users, regional groups) and send targeted reminders without bouncing between a CRM and an email tool. They can cancel a send if an event gets rescheduled or delete a contact who opts out, all in the same Switchy thread where they're planning the event agenda. This works when your lists are under 2,000 contacts total and your send cadence is predictable. If you're sending to 10,000+ contacts or need real-time open tracking, you'll outgrow this setup fast. For small community teams sending 50-300 emails per event, this MCP keeps the workflow tight.
Frequently asked
What does the Resend MCP let me do in Switchy?
It connects your Resend account so AI agents can send transactional emails, manage contact lists, and handle domain setup without leaving the workspace. You can schedule campaigns, cancel queued sends, and sync audience data directly through prompts. It's built for teams who want AI to trigger customer emails based on workflow context, not just copy-paste API calls.
Do I need admin access to connect Resend?
You need a Resend API key with write permissions. That typically means owner or admin access to the Resend account, since the key can create domains, delete contacts, and send emails on your behalf. Read-only keys won't work. Generate the key in Resend's dashboard under API Keys, then paste it into Switchy's connection flow.
Can the Resend MCP read my sent email history?
No. The MCP can cancel scheduled emails and create new sends, but it doesn't expose a tool to retrieve past message content or delivery logs. If you need to audit what was sent, check Resend's dashboard or use their REST API directly. The integration focuses on outbound actions, not forensics.
Why use this instead of Resend's API in my codebase?
The MCP removes the need to write integration glue. Your team describes what they want in plain English—"send a welcome email to new signups in the staging audience"—and the AI handles the API calls. It's faster for one-off campaigns and exploratory work. For high-volume production sends with custom retry logic, stick with the API.
Who on the team should connect our Resend account?
Whoever owns your transactional email setup—usually a developer or growth lead. They'll need the API key and should understand which domains are verified in Resend. Once connected, any Switchy workspace member can prompt the AI to send emails, so set clear team guidelines about who approves outbound campaigns.