Bring Email Testing
to Claude Desktop
Learn how to connect MailSlurp to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect MailSlurp to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
MailSlurp in Claude Desktop
MailSlurp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MailSlurp to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.