Log inSubmit server
Mailtrap logo

Mailtrap

Connects AI assistants to Mailtrap for email sending, testing, templates, delivery logs, contacts, domains, and account management.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Mailtrap

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mailtrap": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-mailtrap"
      ],
      "env": {
        "MAILTRAP_API_TOKEN": "YOUR_VALUE_HERE",
        "MAILTRAP_ACCOUNT_ID": "YOUR_VALUE_HERE",
        "DEFAULT_FROM_EMAIL": "YOUR_VALUE_HERE",
        "MAILTRAP_SANDBOX_ID": "YOUR_VALUE_HERE",
        "MAILTRAP_TEST_INBOX_ID": "YOUR_VALUE_HERE",
        "MAILTRAP_ORGANIZATION_ID": "YOUR_VALUE_HERE",
        "MAILTRAP_ORGANIZATION_API_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 125 tools correctly (Today).

Overview

The Mailtrap MCP server connects MCP-compatible assistants to Mailtrap’s email delivery platform. It supports sending transactional and bulk messages, testing email in Email Sandbox, managing templates and contacts, and reviewing delivery data through natural-language requests. Account resources such as sending domains, webhooks, suppressions, billing usage, and access settings are also covered. Reach for it when an agent needs to perform or investigate Mailtrap email operations from an AI client.

Use cases

  • Send transactional email from an AI assistant
  • Test messages in a Mailtrap Email Sandbox
  • Search delivery logs and investigate bounces
  • Manage templates, contacts, and sending domains
  • Review email delivery and engagement statistics

Key features

  • Transactional and bulk email sending
  • Email Sandbox testing and diagnostics
  • Template and contact management
  • Email log and delivery analysis
  • Sending domain, webhook, and suppression management
  • Account and organization administration

Tools125

What Mailtrap lets your agent do. Expand a tool for its parameters.

Verified live~23.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 45d

What it can do

From the 125 tools this server returned when we ran it; 125 declare their own safety hints.

Can delete or modify data · 43Handles credentials · 15Makes network requests · 13Read-only tools · 82
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age567 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · mcp-mailtrap (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars66Stargazers on the source repository.
npm downloads2.1kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed125Callable tools this server registers over MCP.

How Mailtrap works

What Mailtrap MCP server does

The Mailtrap MCP server exposes Mailtrap account operations to MCP-compatible AI assistants. It is intended for teams that use Mailtrap for transactional or bulk email and want an agent to work with those operations through natural-language prompts.

Supported areas include sending messages through Mailtrap’s email API and SMTP-related workflows, including batch and template-based email. Agents can also use Email Sandbox for testing and inspect message content, headers, attachments, spam scores, and HTML client compatibility.

The Mailtrap MCP server also covers operational email work. It can search email logs, inspect event history, review delivery and bounce information, and analyze open, click, and spam rates. Other supported areas include templates, contacts and lists, sending domains, DNS verification, webhooks, suppressions, billing usage, permissions, API tokens, and sub-accounts.

How it works

The server runs as an MCP process and uses a Mailtrap API token to connect an AI client to the account. Once registered in the client configuration, users can ask the assistant to send or test email, locate messages in logs, manage Mailtrap resources, or review account data.

Operations accept fields appropriate to the request. Email-related inputs include sender and recipient addresses, carbon-copy and blind-carbon-copy recipients, subject, plain text or HTML content, templates, template variables, categories, reply-to values, custom variables, and headers. Log searches can use pagination, date ranges, sender and recipient filters, status filters, subject filters, sending-domain filters, and sending streams.

Setup and configuration

Create a Mailtrap account, verify a sending domain, obtain an API token, and find the Account ID in Mailtrap account management. The server can be installed with npx -y mcp-mailtrap, run from Docker, installed through Smithery, or packaged as an MCPB bundle.

MAILTRAP_API_TOKEN is required for all functionality. MAILTRAP_ACCOUNT_ID is needed for templates, statistics, email logs, sandbox message operations, sending domains, and suppressions, but is optional for the documented send, campaign, company-information, and tracking-opt-out operations.

DEFAULT_FROM_EMAIL provides a fallback sender. MAILTRAP_SANDBOX_ID provides a default test inbox, while MAILTRAP_TEST_INBOX_ID remains available as a legacy fallback. Organization operations additionally use MAILTRAP_ORGANIZATION_ID and MAILTRAP_ORGANIZATION_API_TOKEN.

Tools and capabilities

The Mailtrap MCP server supports these practical workflows:

  • Send transactional, bulk, batch, and template-based email.
  • Test messages in Email Sandbox and inspect their rendered and diagnostic data.
  • Manage templates, contacts, lists, custom fields, events, imports, and exports.
  • Search email logs and review delivery, bounce, open, click, and spam information.
  • Manage sending domains, DNS verification, webhooks, and suppressions.
  • Review billing usage and administer account access, permissions, API tokens, and sub-accounts.

Limitations and notes

The server requires valid Mailtrap credentials and access to the relevant account resources. Not every operation uses the same prerequisites: the Account ID is conditional, and organization functions require separate organization settings and an organization-scoped token. Configuration changes require restarting the MCP server. Sandbox and sender defaults can be overridden through tool parameters, allowing calls to target a different inbox or sender.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Mailtrap

Mailtrap is an MCP server that connects MCP-compatible AI assistants to the Mailtrap email delivery platform. Its main tools support transactional and bulk email sending, Email Sandbox testing, template and contact management, email-log searches, delivery analysis, sending-domain administration, webhooks, suppressions, and account resource management.

Install it with `npx -y mcp-mailtrap` in an MCP client configuration. You can also run the published Docker image, use Smithery CLI, or install an MCPB bundle from the project releases. Configure the required Mailtrap token and any account or sandbox settings before starting the client.

Yes, Mailtrap works with Cursor. Add an `mcpServers` entry that runs `npx -y mcp-mailtrap`, then provide `MAILTRAP_API_TOKEN` and the other applicable environment variables.

The server always requires `MAILTRAP_API_TOKEN`. `MAILTRAP_ACCOUNT_ID` is needed for many account, template, statistics, log, sandbox, domain, and suppression operations, but not for several documented send and account-information tools. Sender, sandbox, and organization variables are optional or operation-specific.

Yes, the server supports Mailtrap Email Sandbox workflows. An agent can send test messages and inspect message content, headers, attachments, spam scores, and HTML client compatibility. Set `MAILTRAP_SANDBOX_ID` as a default inbox or provide the sandbox identifier through the relevant tool parameters.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMailtrap AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mailtrap?style=directory)](https://allmcps.com/mcp/mailtrap)
HTML Embed
<a href="https://allmcps.com/mcp/mailtrap"><img src="https://allmcps.com/api/badge/mailtrap?style=directory" alt="Mailtrap on AllMCPs" /></a>