Bring Email Testing
to VS Code Copilot
Learn how to connect MailSlurp to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings MailSlurp data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
MailSlurp in VS Code Copilot
MailSlurp and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MailSlurp to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.