Labsco
MCP SERVER

Mailtrap

by railsware ↗

Send email through Mailtrap and test it safely — deliver or batch transactional and bulk mail, inspect sandbox messages with spam scores, manage templates and contacts.

Email: Mailboxes & Delivery✓ Verified
Summary
Test the email against a spam filter before you ever deliver it.

The sandbox is the reason to reach for this over a plain send-only integration: send-sandbox-email lands in a test inbox where get-sandbox-message-spam-score and get-sandbox-message-html-analysis tell you the SpamAssassin score and the client-rendering problems before a real recipient sees it. When you do go live, get-sending-stats and the suppression tools give you the deliverability side that a bare SMTP relay does not.

What it is

A server for the Mailtrap email platform: 105 tools across live sending, the sandbox testing environment, templates, contacts and contact lists, inbound streams, sending stats and suppressions.

What you get
  • Live sending: send-email through the Mailtrap Email API, plus batch-send-transactional-email and batch-send-bulk-email for many messages in one call over the respective streams
  • A full sandbox for testing without delivering: send-sandbox-email to a test inbox, get-sandbox-messages and show-sandbox-email-message to read them, and project/inbox management (create-sandbox-project, create-sandbox-inbox with its SMTP credentials, clean-sandbox-inbox)
  • Deep message inspection in the sandbox: get-sandbox-message-spam-score returns the SpamAssassin report, get-sandbox-message-html-analysis checks client compatibility, and the html, text, raw, eml, headers and source of a message plus its attachments are all readable
  • Templates managed end to end — create-template, list-templates, get-template, update-template and delete-template
  • Contacts and lists: create-contact, update-contact, contact lists and custom contact fields, plus create-contact-import and create-contact-export for bulk moves
  • Deliverability visibility: get-sending-stats for delivery, bounce, open, click and spam rates, and list-suppressions / delete-suppression to manage the suppression list
  • Inbound streams handled with their own create/list/get/update/delete tools
Requirements

A Mailtrap API token in MAILTRAP_API_TOKEN, required for everything. MAILTRAP_ACCOUNT_ID is required for templates, stats, email logs, the sandbox list and sending domains, and optional for the send tools. DEFAULT_FROM_EMAIL sets the sender when a send omits from. Node, run as npx mcp-mailtrap. Organization tools need a separate MAILTRAP_ORGANIZATION_API_TOKEN.

Setup effort

One command plus a key — npx @smithery/cli install mailtrap, then supply credentials