Resend MCP
Send and manage transactional email through Resend.
Verdict
Common use cases
- Send customer onboarding emails from support chat
- Draft and dispatch product update announcements
- Test transactional email templates before deploy
- Automate follow-up sequences after sales calls
- Track delivery status for time-sensitive messages
Integration
- Vendor
- Resend MCP
- Category
- other
- Auth
- OAUTH2
- Composio slug
resend_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations. 2. Find Resend MCP in the list and click Connect. 3. You'll be redirected to Resend's OAuth consent screen — sign in with your Resend account credentials. 4. Review the requested scopes (typically email:send and domain:read) and click Authorize. 5. Switchy confirms the connection and returns you to the integrations page. 6. Open any Project and type '@Resend' to verify the MCP appears in the mention menu. 7. Test the connection by asking '@Resend check my sending domain status' — if it returns domain details, you're ready. 8. To send a test email, try '@Resend send a test message to [your-email] with subject Test from Switchy' and confirm delivery in your inbox.
What teammates see: by default, memories from Resend MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Send Welcome Email
@Resend send a welcome email to alex@example.com with subject 'Welcome to our platform' and a friendly intro paragraph mentioning their account is ready.
Check Domain Status
@Resend check the verification status and DNS records for my primary sending domain.
Draft Template Email
@Resend draft an HTML email template for a password reset notification with a clear call-to-action button and 24-hour expiry notice.
Batch Send Invites
@Resend send invitations to jordan@example.com, sam@example.com, and casey@example.com for our Q2 planning session on March 15th, personalizing each with their first name.
Track Recent Sends
@Resend show me delivery status and any bounces for emails sent from my account in the past day.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@resend send a transactional email to user@example.com with subject 'Password Reset' and a plain-text body containing the reset link https://app.example.com/reset/abc123
Email queued successfully. Message ID: msg_2kX9pLmN4qR7sT1vW. Sent from: noreply@yourdomain.com to user@example.com. Subject: Password Reset. The email will be delivered within seconds, and you can track opens/clicks in the Resend dashboard. This example assumes your domain is verified and the 'from' address matches your configured sender.
Demonstrates the core send capability. Requires OAuth2 scope for sending emails and a verified domain in your Resend account. The MCP does not validate recipient addresses or retry failed deliveries—check the Resend dashboard for bounce/complaint handling.
@resend fetch the delivery status and open/click metrics for message ID msg_2kX9pLmN4qR7sT1vW from the last password reset campaign
Message msg_2kX9pLmN4qR7sT1vW: Delivered at 2025-01-15 14:32 UTC. Opened once at 14:35 UTC. Clicked once at 14:36 UTC. No bounces or complaints. Recipient: user@example.com. This illustrative response shows typical tracking data—actual fields depend on whether you enabled open/click tracking when sending.
Shows read-only analytics retrieval. Requires OAuth2 scope for reading message data. Open/click tracking only works if enabled at send time and if the recipient's email client loads images. Resend retains event data for 30 days by default.
@resend list all emails sent in the last 24 hours with status 'bounced' and summarize the most common bounce reasons
Found 3 bounced emails in the last 24 hours: msg_3aB4cD (hard bounce: mailbox does not exist), msg_5eF6gH (soft bounce: mailbox full), msg_7iJ8kL (hard bounce: domain not found). Most common reason: hard bounces due to invalid recipient addresses. Consider cleaning your email list to reduce bounce rate and protect sender reputation. This example assumes the MCP can filter by status and timestamp.
Combines list filtering with AI synthesis. Requires OAuth2 scope for reading message history. High bounce rates can harm deliverability—Resend may throttle or suspend accounts with sustained bounce rates above 5%. Use this workflow to audit send quality before scaling campaigns.
Use-case deep-dives
Automating executive summaries without a separate reporting tool
A 6-person ops team compiles a weekly metrics summary every Friday: revenue, support volume, top bugs. They used to paste it into a Google Doc, then manually email the link to 8 stakeholders. Now the AI generates the summary from Switchy's chat history, formats it as HTML, and sends it through Resend to the distribution list. The OAuth2 setup means the team lead authorizes once, and everyone on the workspace can trigger sends without touching credentials. This breaks down if your stakeholder list changes weekly—Resend MCP doesn't sync contact lists, so you'd hard-code emails or maintain them in a separate CRM. For static lists under 20 people, it's faster than setting up Mailchimp.
Frequently asked
What does the Resend MCP do in Switchy?
The Resend MCP connects your team's Resend account to Switchy's AI workspace, letting Claude access your transactional email data and operations. Your team can query email delivery stats, check bounce rates, or pull campaign performance without leaving the conversation. It's useful for support teams debugging delivery issues or marketers reviewing send metrics in context.
Does Resend MCP require OAuth or just an API key?
Resend MCP uses OAuth2, so you'll authorize through Resend's standard flow rather than copying API keys. This means Switchy gets scoped access to your account without handling raw credentials. You'll see which permissions the integration requests during setup — typically read access to domains, emails, and analytics. One team member with Resend admin rights should connect it.
Can the Resend MCP send emails from Switchy?
That depends on which tools Resend exposes through the MCP protocol. Most email MCPs focus on read operations — pulling logs, checking status, analyzing deliverability. If you need to send transactional emails, you'll likely still use Resend's API directly or their dashboard. Check the tool list once it populates to see exactly what's available.
How is this different from just using Resend's dashboard?
The MCP brings Resend data into your AI workflow, so Claude can answer questions like "why did this email bounce" or "show me opens for the last campaign" without you switching tabs. The dashboard is still better for composing templates or configuring domains. Think of the MCP as a query layer, not a replacement for Resend's full interface.
Who on the team should connect the Resend MCP?
Whoever has admin access to your Resend account should handle the OAuth setup. Once connected, any Switchy member can use the integration in conversations — they don't need separate Resend logins. If your team shares one Resend workspace, one connection covers everyone. The MCP doesn't consume Resend API quota separately from your normal usage.