MailSlurp MCP. Automate Email Testing & Manage Virtual Inboxes

Forget setting up a real testing environment. You connect your AI client, and it handles all the email junk for you. This MailSlurp MCP Server lets your agent run automated email tests straight from natural language prompts—it's built for people who need to validate user signups or test complex transaction alerts without ever touching a live inbox.

Setting Up Your Virtual Test Bench

You can start by generating completely fresh, temporary email addresses using create_random_inbox. This gives your agent a brand-new virtual address it can use for any given test run. You'll also need to know what you've got going on; running list_all_inboxes lets you pull up a clean rundown of every single virtual inbox currently linked to your account.

When the job is done and that mailbox isn't needed anymore, you can delete it entirely using delete_specific_inbox, wiping out both the address and all associated emails.

Sending Messages Out

Need to trigger a test? You use send_email_from_inbox to send an outgoing email right from one of your active MailSlurp addresses. It's simple: tell it who to send it to, and your agent handles the rest.

Watching for Replies (The Polling Mechanics)

This is where it gets powerful. You don't want your test script hanging around, waiting forever for an email that might never come. Your agent can actively monitor a mailbox using specialized polling methods. If you just need to know the second an email lands, wait_for_latest_email monitors the inbox and hands over the content immediately when it arrives.

But if your process requires multiple messages—say, checking for three different confirmation emails—you use wait_for_email_count. This function pauses execution until a target mailbox hits a specific number of messages you set.

Before diving into waiting, you can get a quick overview using list_inbox_emails, which pulls back a summary list of every email received by that virtual address. It's a fast check to see if anything landed in the interim.

Deep Message Inspection and Data Retrieval

When an email comes through, you need more than just a subject line. You need the whole deal. To get all the guts of a message, use get_email_details with a specific message ID. This call doesn't just give you text; it retrieves everything: the full HTML body for display, the plain text version, crucial technical headers, and any attached files.

It gives you the complete metadata package on that single received email.

Workflow Cleanup

Cleanup is routine but necessary. After you’ve pulled all your data, remember you can use delete_specific_inbox to completely remove an entire virtual inbox. You also get granular control over individual messages; you can delete specific emails using the system's internal message identifiers.