Bring Email Sandbox
to VS Code Copilot
Learn how to connect Mailtrap to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Mailtrap MCP Server?
Connect your Mailtrap account to any AI agent and manage email testing and delivery through natural conversation.
What you can do
- Email Sending — Send transactional emails via the Mailtrap API
- Inbox Testing — Browse testing inboxes and inspect captured emails
- Message Analysis — Analyze email HTML, spam scores, and headers
- Delivery Analytics — Track opens, clicks, bounces, and delivery rates
- Project Management — Manage testing projects and inboxes
- Account Management — Switch between connected accounts and domains
How it works
1. Subscribe to this server
2. Enter your Mailtrap API Key and Account ID
3. Start testing and sending email from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — test email flows safely in staging
- QA Engineers — verify email rendering and spam scores
- Operations — monitor production transactional delivery
Built-in capabilities (12)
Delete all emails in inbox
Delete captured email
Get domain details
Get message metadata
Get email HTML body
Get user accounts
List account projects
List messages in inbox
List virtual inboxes
List sending domains
Send email in production
Send test email to sandbox
Why VS Code Copilot?
GitHub Copilot Agent mode brings Mailtrap data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 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
Mailtrap in VS Code Copilot
Mailtrap and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mailtrap 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 Mailtrap in VS Code Copilot
The Mailtrap 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 12 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
Mailtrap for VS Code Copilot
Every tool call from VS Code Copilot to the Mailtrap MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I both test and send emails with Mailtrap?
Yes. Mailtrap supports both Email Testing (capturing emails in staging) and Email Sending (transactional delivery in production).
Does Mailtrap require an Account ID?
Yes. You need both an API Key and Account ID to authenticate via Bearer token against mailtrap.io/api.
Can I analyze spam scores and HTML rendering?
Yes. Mailtrap analyzes captured emails for spam score (SpamAssassin), blacklists, HTML errors, and client support.
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.