← Explore all mcp servers

EMAIL / Mailtrap / Railsware

Mailtrap MCP

Send or sandbox email, inspect delivery logs and statistics, and manage templates, domains, contacts and account resources.

“Send or sandbox email, inspect delivery logs and statistics, and manage templates, domains, contacts and account resources.”

01 / THE REASONING

Why this made the selection.

  • Send or sandbox email, inspect delivery logs and statistics, and manage templates, domains, contacts and account resources.
  • The setup documentation makes this operating boundary explicit: Production sending and Email Sandbox are separate tools. Organization operations require MAILTRAP_ORGANIZATION_ID and a separate MAILTRAP_ORGANIZATION_API_TOKEN.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md
  • LICENSE.txt
  • package.json
  • src/client.ts

Our findings

  • Production sending and Email Sandbox are separate tools. Organization operations require MAILTRAP_ORGANIZATION_ID and a separate MAILTRAP_ORGANIZATION_API_TOKEN.
  • An ordinary API token is not the organization token. Account administration can create or revoke tokens and change permissions, and production sends are not sandboxed merely because a sandbox ID is configured.

Not established by this review

  • No server installation, authentication, live tool execution or isolation test was performed.
  • Package/container parity with the pinned source and transitive dependency security were not established.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx -y mcp-mailtrap

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Register npx -y mcp-mailtrap with MAILTRAP_API_TOKEN; provide MAILTRAP_ACCOUNT_ID for account-level resources, DEFAULT_FROM_EMAIL for a default sender and MAILTRAP_SANDBOX_ID for sandbox sends.
  2. Verify the connected account, available tools and target resource before authorizing mutations.

Before you start

  • Pinned package Node.js requirement: >=16.20.1.
  • A compatible local process MCP client.
  • Production sending and Email Sandbox are separate tools. Organization operations require MAILTRAP_ORGANIZATION_ID and a separate MAILTRAP_ORGANIZATION_API_TOKEN.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/mailtrap/mailtrap-mcp/blob/712d7ade3db16c4fa304b23e9d8d57a119972a66/README.md

    Supports: description, setup, capabilities, review, limitations

  2. https://github.com/mailtrap/mailtrap-mcp/blob/712d7ade3db16c4fa304b23e9d8d57a119972a66/LICENSE.txt

    Supports: license

  3. Pinned package metadata ↗Checked

    https://github.com/mailtrap/mailtrap-mcp/blob/712d7ade3db16c4fa304b23e9d8d57a119972a66/package.json

    Supports: install, language, review

  4. https://github.com/mailtrap/mailtrap-mcp/blob/712d7ade3db16c4fa304b23e9d8d57a119972a66/src/client.ts

    Supports: review, install, access, limitations

Evidence & Ask