Mailtrap
Connect Mailtrap sending, domains, suppressions, and analytics so your agent can test and operate email flows while you build.
Overview
Mailtrap is an MCP server for the Build phase that sends mail and manages Mailtrap domains, suppressions, and delivery analytics for agent workflows.
What is this MCP server?
- Send email and manage Mailtrap sending domains from MCP tools
- Work with suppression lists to respect bounces and blocks
- Pull delivery analytics for troubleshooting message paths
- Version 1.0.2 with uvx PyPI and Docker OCI stdio packages
- Email operations MCP—distinct from markdown template or UX copy skills
- 2 install paths: PyPI (uvx) and OCI Docker
- Stdio transport type
Community signal: 25 GitHub stars.
What problem does it solve?
Email integration work stalls when you manually toggle Mailtrap settings and copy API responses instead of letting the agent drive sends, lists, and stats.
Who is it for?
Builders using Mailtrap who want MCP-driven send tests, domain tweaks, and suppression checks during backend and notification implementation.
Skip if: Teams on a different ESP with no Mailtrap account, or anyone who only needs static HTML previews without API automation.
What do I get? / Deliverables
After installation, your agent can operate Mailtrap sending and list APIs so you iterate on email features with observable delivery data in the same session.
- Mailtrap send, domain, and suppression tools exposed to the agent
- Repeatable agent-driven email integration tests
- Delivery analytics accessible during debug sessions
Recommended MCP Servers
Journey fit
Mailtrap MCP is registered during Build when email infrastructure is coded and validated against a real provider API. Integrations covers ESP tooling; Mailtrap also supports pre-production email testing common before Ship.
How it compares
Mailtrap ESP MCP bridge, not a Ship-phase security audit or content-marketing skill.
Common Questions / FAQ
Who is com.mcparmory/mailtrap for?
Indie developers and small teams on Mailtrap who integrate email via MCP-enabled coding assistants.
When should I use com.mcparmory/mailtrap?
Use it while building or debugging email features that need sends, domain config, suppressions, or analytics from Mailtrap.
How do I add com.mcparmory/mailtrap to my agent?
Add the stdio server using mcparmory-mailtrap with uvx or the ghcr.io/mcparmory/mailtrap container, provide Mailtrap API credentials, and restart your MCP client.