Mailtrap MCP server

What the model can do

Mailtrap email delivery: sent-email logs with status and each message's delivery events (delivered, opened, clicked, bounced, spam, rejected), sending stats by domain, category, mailbox provider or day, sending domains and their verification, suppressed addresses, email campaigns and their stats, marketing contacts and lists, templates, sandbox test inboxes and inbound inboxes. Can send email, send a test into a sandbox, reply to or forward an inbound message, manage contacts, lists, templates and suppressions, and start, schedule, cancel or stop a campaign, each only when asked.

Reads

• mailtrap_email_logsMailtrap sent-email logs, newest first: message id, status (delivered, not_delivered, enqueued, opted_out), sent time, from, to, subject, stream…
• mailtrap_sending_statsMailtrap sending stats over a date window: delivered, bounced, opened, clicked and spam counts and rates, overall or broken down by sending domain…
• mailtrap_domainsMailtrap sending domains: id, name, compliance status (compliant, unverified_dns, under_review, suspended …)…
• mailtrap_suppressionsMailtrap suppressed addresses (no mail goes to them): address, reason (hard bounce, unsubscription, spam complaint, manual import), when, stream…
• mailtrap_campaignsMailtrap email campaigns, newest first: id, name, state (draft, scheduled, started, under_review, finished, failed …), scheduled time…
• mailtrap_contactsMailtrap marketing contacts: id, email, name, subscribed or unsubscribed, list ids, created and updated.
• mailtrap_templatesMailtrap email templates: id, uuid (what a send uses), name, category, subject, created and updated.
• mailtrap_sandbox_messagesMailtrap sandbox (testing) inboxes, which capture mail instead of delivering it.
• mailtrap_inbound_messagesMailtrap inbound email.

Acts, when you ask

These change something in Mailtrap. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• mailtrap_send_emailSend an email through Mailtrap to real recipients, on the transactional stream (one-to-one mail) or the bulk stream (newsletters, announcements).
• mailtrap_send_sandbox_emailSend a test email into a Mailtrap sandbox inbox.
• mailtrap_reply_inboundAnswer an inbound Mailtrap message by email.
• mailtrap_create_contactAdd a marketing contact to Mailtrap, optionally into lists.
• mailtrap_update_contactChange a Mailtrap marketing contact: its email, custom fields, lists it is added to or removed from, or mark it unsubscribed.
• mailtrap_delete_contactDelete a Mailtrap marketing contact by id or email.
• mailtrap_create_contact_listCreate an empty Mailtrap contact list.
• mailtrap_create_suppressionSuppress an address on a Mailtrap sending domain and stream, so no further email goes to it from there, including password resets and receipts.
• mailtrap_delete_suppressionLift a Mailtrap suppression so email can go to that address again.
• mailtrap_create_templateCreate a Mailtrap email template (name, category, subject, and text and/or HTML body).
• mailtrap_update_templateChange a Mailtrap email template.
• mailtrap_delete_templateDelete a Mailtrap email template.
• mailtrap_start_campaignSend a draft Mailtrap email campaign to its whole audience.
• mailtrap_schedule_campaignSchedule a draft Mailtrap email campaign to send to its whole audience at a time 5 minutes to 1 month ahead.
• mailtrap_cancel_campaignCancel a scheduled Mailtrap email campaign before it sends; it goes back to draft and nobody is emailed.
• mailtrap_terminate_campaignStop a Mailtrap email campaign that is sending (started, queued or paused).

Connect it

First connect Mailtrap on Dashboard → Connections, then add Memtro to your client once. The Mailtrap tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Mailtrap connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Was the password reset to priya@acme.example delivered?
• › What was our bounce rate by mailbox provider last week?
• › How did the October newsletter campaign perform?
• › Is our sending domain verified?
• › Cancel the scheduled November newsletter

Questions

Is this an official Mailtrap MCP server?

No. It is Memtro's MCP server with Memtro's Mailtrap connector behind it: the connector reads Mailtrap through its API with the credentials you connect on Dashboard → Connections, and Mailtrap publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Mailtrap?

Only when you ask, and only what it has been granted: send an email through the transactional or bulk stream (billed, reaches real recipients); send a test email into a sandbox inbox (captured, not delivered); reply to, reply-all or forward an inbound message (reaches real recipients); create, update or delete a marketing contact; create a contact list; suppress an address so no more mail goes to it, or lift a suppression; create, update or delete an email template; start, schedule, cancel or terminate an email campaign. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Email, calendar and chat

• AgentMail MCP server
• Gmail MCP server
• Google Calendar MCP server
• Slack MCP server
• Outlook Mail MCP server
• Outlook Calendar MCP server