Server facts
mailtrap-mcp
Project
- Author
- railsware
- Repository
- github.com/railsware/mailtrap-mcp
- Website
- mailtrap.io
- License
- MIT
- Category
- Communication
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 66
- Last commit
- Data as of
Tags
- email api
- mailtrap
- transactional emails
Overview
Mailtrap’s testing and sending workflows connect to MCP clients through mailtrap-mcp. Developers can send transactional or bulk messages, use templates with variable substitution, and batch messages with shared defaults and individual overrides. Sandbox tools send test messages without delivering them to recipients, organize projects and inboxes, and inspect message bodies, headers, attachments, spam reports, and HTML compatibility findings. For delivery investigations, the integration provides filtered email logs, message event histories, and sending statistics grouped by dimensions such as domain or category. Template editing and sending-domain management support the surrounding email setup.
Beyond testing and delivery, tools manage contacts, list memberships, custom fields, imports, and exports. Campaign workflows cover drafting, starting, scheduling, cancelling scheduled sends, and reviewing performance. Inbound mail tools organize folders and inboxes, retrieve messages and conversation threads, and send replies or forwards as real email. Administrative operations cover webhooks, suppressions, billing usage, account access, permissions, API tokens, and organization sub-accounts. The server uses Node.js and communicates over stdio; its documented client configurations include Claude Desktop, Cursor, and VS Code.
mailtrap-mcp setup notes
- mailtrap-mcp records stdio only; confirm a network transport upstream before planning remote access.