Resend MCP. Manage domains, contacts, and emails in one chat session.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Resend gives your AI agent full control over email infrastructure. Send transactional or broadcast emails, manage domains by checking DNS records, audit API keys, and segment contacts directly from any client.
It handles the entire lifecycle of your outgoing messages.
What your AI agents can do
Add domain
Adds a new domain you want to send from and returns the required DNS records for setup.
Create contact
Adds a specific email address to an existing audience list.
Get domain
Retrieves detailed information about a single sending domain you use.
Sends transactional or bulk emails via an API call, returning an ID you can use to check delivery status.
Retrieves detailed metadata for a sent email, showing if it bounced, was opened, or clicked.
Lists existing verified domains and retrieves the necessary DNS records to set up new sending identities.
Lists all defined email audiences, then pulls specific contacts from those groups for targeted campaigns.
Provides a list of every active API key associated with the account and its permission scopes.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Resend MCP Server: 10 Tools for Email Ops
These tools let you run the full email lifecycle—sending messages, managing sending domains, auditing users, and tracking results—all through conversational commands.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Resend on Vinkius019d75feadd domain
Adds a new domain you want to send from and returns the required DNS records for setup.
019d75fecreate contact
Adds a specific email address to an existing audience list.
019d75feget domain
Retrieves detailed information about a single sending domain you use.
019d75feget email
Checks the delivery status of a specific, previously sent email ID.
019d75felist api keys
Lists every active API key connected to your Resend account for security auditing.
019d75felist audiences
Retrieves a list of all the user groups (audiences) you have set up.
019d75felist contacts
Lists all contacts contained within a specific, chosen audience group.
019d75felist domains
Shows all verified sending domains that are currently active and ready to use.
019d75fesend batch emails
Sends multiple emails at once, requiring 'from', 'to', 'subject', and HTML content for each message.
019d75fesend email
Sends a single transactional email and returns a unique ID so you can track its delivery status later.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Resend, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Resend. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Debugging email delivery shouldn't require jumping between three different tabs.
Today, if a critical transactional email fails, you’re stuck clicking through the dashboard: first to check domain status, then to find the recipient list, and finally trying to locate the specific message ID to see if it bounced. It's slow, prone to context switching, and wastes time.
With Resend MCP Server, your AI agent handles this entire flow conversationally. You ask for delivery info on a specific email using `get_email`. The agent instantly checks the metadata—bounced? opened? delivered?—and tells you exactly why it failed. Done.
Resend MCP Server: Control your domains and contact lists.
Manually verifying domain records (SPF/DKIM) for a new campaign requires logging into the DNS panel, checking multiple record types, and waiting for propagation—a huge bottleneck. You're blocked until it clears.
Now, your agent handles that. You ask the server to check your domain status using `get_domain`. It instantly pulls the records and tells you what needs fixing so you can send emails right away.
What you can do with this MCP connector
You gotta connect your AI agent to this server so it can take full command of your email infrastructure. You manage everything—sending, domains, contacts—right from your client without leaving your workspace.
Sending Emails & Tracking Deliveries: When you're ready to send messages, your agent handles both single and bulk operations. For a quick transactional blast, use send_email; that fires off one email and returns a unique ID for later tracking. If you’ve got a big campaign going, just run send_batch_emails. This tool is built for volume; it takes the 'from', 'to', 'subject', and HTML content for every single message in the batch.
Once those emails go out, don't assume they landed. You check the full delivery status using get_email, which pulls detailed metadata telling you if the email bounced back, or if a user actually opened it or clicked any links inside.
Domain Management & Setup: To make sure your mail looks legit, you need to control your sending identities. First, run list_domains to see all the verified domains ready for use. If you don't have one set up yet, you use add_domain. This doesn't just add a name; it gives you the exact required DNS records you gotta implement on your end to make sure that domain is legit and operational.
You can also pull deep details about any single sending identity using get_domain.
Audience & Contact Segmentation: To target people, you need to know who they are. Start by seeing every user group or audience list you've built up with list_audiences. Once you pick a specific group, you pull the whole roster of emails from that section using list_contacts. If your campaign spots a new lead, you don't have to do it manually; you use create_contact to add that specific email address right into an existing audience list for future sends.
Security & Account Auditing: Keep things tight and secure. You audit every piece of the system by calling list_api_keys. This shows you a full rundown of every active API key connected to your account, letting you see exactly what permissions are attached to each one. Your agent manages the entire lifecycle—from validating an SPF record for a new domain to sending out high-volume blasts and checking bounce rates, all in chat commands.
019d75fe-d940-70eb-8ea8-0b5e93c292db 
How Resend MCP Works
- 1 Subscribe to this server on Vinkius and provide your Resend API Key.
- 2 Ask your AI agent to perform an action, like 'List all verified sending domains.'
- 3 The agent executes the tool call, fetches the data (e.g., list of domains), and presents a clear summary back to you.
The bottom line is: it turns complex email API calls into simple conversations with your AI client.
Who Is Resend MCP For?
This server is built for people who own the infrastructure, not just the campaigns. It's for the DevOps engineer tired of switching between the code editor and the Resend dashboard to audit keys. It’s for the developer who needs to test email logic without running a local SMTP server. And it’s for the marketing operations lead who needs immediate feedback on domain health before launching a campaign.
Auditing API key permissions using list_api_keys and ensuring proper DNS records via add_domain.
Sending test emails for a new feature using send_email and debugging delivery issues with get_email.
Segmenting large lists of users by calling list_audiences then pulling specific contacts via list_contacts before sending a campaign.
What Changes When You Connect
- Domain health is instant. You check domain status using
get_domainor list all domains withlist_domains. This lets you validate sender identity before a single email goes out, preventing high bounce rates due to bad DNS records. - Segmentation gets easy. Instead of manually exporting lists, you can run
list_audiences, then uselist_contactsto get the exact list of subscribers needed for a targeted campaign. - Debugging is fast. After running a campaign, you don't wait on a dashboard. You check delivery status immediately using
get_emailwith the returned email ID, so you know if it hit the inbox or bounced. - Auditing is simple. Need to know who has access? Run
list_api_keys. It shows every active key and exactly what permissions they have—critical for security hygiene. - Sending flexibility. You can handle both single messages (via
send_email) and massive campaigns (usingsend_batch_emails), all from the same chat interface.
Real-World Use Cases
Onboarding a new product feature.
A developer needs to test a critical welcome flow. Instead of setting up a local server, they ask their agent to 'Send a welcome email to jane@example.com.' The agent uses send_email, gets the ID, and then runs get_email right after to confirm it was delivered successfully.
Pre-launch campaign prep.
The marketing team needs to know if their primary sending domain is ready. They first use list_domains to check the status, then run get_domain on a specific one to verify all DNS records are correctly configured before building out any lists.
Cleaning up stale contact lists.
An ops engineer suspects some contacts aren't receiving emails. They start by calling list_audiences to see groups, then use list_contacts on the 'Newsletter' group to review the first 50 records and check for suspicious or outdated addresses.
Launching a massive promotional blast.
A team needs to send 100 emails simultaneously. They instruct their agent to 'Send these ten emails.' The agent uses send_batch_emails, ensuring all necessary fields (from, to, subject) are provided in the prompt for high-volume sending.
The Tradeoffs
Assuming perfect data.
Just running a campaign and hoping it works. You skip checking if your contacts or domains are up to date.
→
Always check first: run list_domains then use get_domain. Before sending, list audiences (list_audiences) and audit the contact base with list_contacts.
Ignoring security requirements.
Relying on a single API key for everything because it's 'easier.'
→
Use list_api_keys to see all keys. If you find an unused or overly powerful key, revoke it immediately.
Treating emails as fire-and-forget.
Sending a message and just walking away without confirmation.
→
Always use send_email or send_batch_emails, and then save the returned ID. Use that ID with get_email to confirm delivery status.
When It Fits, When It Doesn't
Use this MCP Server if your job involves managing the entire lifecycle of email communication: from verifying sender identity (via list_domains/get_domain) to segmenting users (list_audiences/list_contacts), and finally executing the send and tracking results (send_email/get_email). You need this server if deliverability is a core operational concern.
Don't use it if your only goal is sending one-off emails to a single, hardcoded address. In that niche case, basic API calls might suffice. However, because you gain access to domain management and contact auditing tools like list_api_keys, this server handles the complexity of scaling from simple sends to complex broadcast operations. It's your full email ops center.
Common Questions About Resend MCP
How do I list all domains with Resend MCP Server? +
You use the list_domains tool. This command shows every verified sending domain currently connected to your account, giving you an immediate view of your available sender identities.
What is the difference between send_email and send_batch_emails? +
send_email sends one message and returns a unique ID for tracking. send_batch_emails sends multiple messages at once, requiring you to list all recipients and content fields in the prompt.
Can I audit my API keys using Resend MCP Server? +
Yes, use the list_api_keys tool. It lists every active key associated with your account, letting you check for unauthorized or outdated credentials.
How do I find contacts in a specific audience list? +
You first call list_audiences to find the ID of the group, and then use the list_contacts tool, referencing that ID, to retrieve all members inside.
How do I use the `add_domain` tool to verify a new sending domain? +
The add_domain tool returns the required DNS records (TXT, CNAME) for your domain. You must copy and paste these specific records into your domain registrar's settings. Once implemented, you can use other tools to check its verification status.
What kind of details does the `get_domain` tool provide about a specific sending domain? +
This tool fetches granular data on one domain ID, including its current verified status, associated region, and ownership metadata. It helps confirm if a domain is ready for live sending.
How do I add a new subscriber using the `create_contact` tool? +
To run create_contact, you must provide three things: the recipient's email address, their display name, and the ID of the target audience. This adds them to your mailing list immediately.
If an email doesn't deliver, how do I check its status using the `get_email` tool? +
You need the unique email ID generated when you originally sent the message. The get_email tool then provides detailed delivery metadata, including bounce reasons or open/click analytics.
Can I send an email with HTML content and track whether it was delivered? +
Absolutely. Use the send_email tool with your HTML body, then use get_email with the returned ID to check delivery status, open events, and bounce details in real time.
How do I check if my sending domain DNS records are correctly configured? +
Run list_domains to find your domain ID, then use get_domain to inspect the full DNS record set (SPF, DKIM, return path). If records are pending, trigger verify_domain to re-check.
Can I add subscribers to an audience for broadcast campaigns? +
Yes. First use list_audiences to get the target audience ID, then call create_contact with the subscriber's email and optional name fields. The contact is immediately available for broadcast targeting.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.