Bring Email Testing
to Cursor
Learn how to connect MailSlurp to Cursor and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the MailSlurp MCP Server?
Connect your MailSlurp account to any AI agent to automate your email testing and asynchronous message management. This MCP server enables your agent to create virtual inboxes, send and receive emails, and handle complex automation scenarios using long-polling 'wait-for' methods directly from natural language interfaces.
What you can do
- Virtual Inbox Management — Create random or custom email addresses and list all managed inboxes in your account
- Email Automation — Long-poll for the latest incoming email or wait until a specific email count is reached for testing suites
- Message Retrieval — List and inspect messages received by any virtual address, including full HTML and text bodies
- Outbound Capability — Send emails directly from any of your MailSlurp addresses programmatically
- Infrastructure Maintenance — Permanently delete individual messages or entire virtual inboxes via simple commands
- Metadata Inspection — Retrieve detailed technical headers and attachment metadata for any received email
How it works
1. Subscribe to this server
2. Enter your MailSlurp API Key (x-api-key)
3. Start managing your virtual email infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- QA Engineers — Automate the verification of user registration flows and transactional alerts via natural language
- Developers — Quickly inspect incoming test emails and manage temporary addresses directly from your IDE
- Product Teams — Monitor and audit automated communication paths and email delivery results effortlessly
Built-in capabilities (8)
Create a new random email address
Delete an inbox and its emails
Get complete content for a specific email
List all MailSlurp inboxes
List emails received by an inbox
Requires recipient and content. Send an email using a MailSlurp address
Wait until an inbox has a certain number of emails
Returns the latest one immediately if present. Long-poll for the next incoming email
Why Cursor?
Cursor's Agent mode turns MailSlurp into an in-editor superpower. Ask Cursor to generate code using live data from MailSlurp and it fetches, processes, and writes. all in a single agentic loop. 8 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
MailSlurp in Cursor
MailSlurp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MailSlurp to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for MailSlurp in Cursor
The MailSlurp MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
MailSlurp for Cursor
Every tool call from Cursor to the MailSlurp MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Inbox ID?
Use the list_all_inboxes tool to see a comprehensive list of all your MailSlurp addresses along with their unique IDs.
What is the benefit of the 'wait-for' tools?
They hold the connection until an email arrives, making it easy to test asynchronous processes (like password resets) without writing complex retry loops.
Where do I find my API Key?
Log in to your MailSlurp dashboard and copy the API key from the Home or API Settings section.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.