Bring Email Sandbox
to Cursor
Learn how to connect Mailtrap to Cursor 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 Cursor?
Cursor's Agent mode turns Mailtrap into an in-editor superpower. Ask Cursor to generate code using live data from Mailtrap and it fetches, processes, and writes. all in a single agentic loop. 12 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
Mailtrap in Cursor
Mailtrap and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Mailtrap 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 Mailtrap in Cursor
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 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
Mailtrap for Cursor
Every tool call from Cursor 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.
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.