Mailtrap vs Email MCP

A side-by-side look at the Mailtrap and Email MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Mailtrap logoMailtrapCommunication · Local subprocess (stdio)Official mailtrap.io MCP server64GoodAuth: not declaredEmail MCP logoEmail MCPCommunication · Local subprocess (stdio)Unified MCP server for email across Gmail (REST API), Outlook (Microsoft Graph), iCloud, and generic IMAP/SMTP. 24 tools for search, send, organize, and batch-manage emails with built-in OAuth2 and encrypted credential storage.68GreatAuth: other

Verdict: choose Mailtrap for communication work as a local process; choose Email MCP for communication as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Mailtrap logoChoose Mailtrap when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: MAILTRAP_API_TOKEN, MAILTRAP_ACCOUNT_ID, DEFAULT_FROM_EMAIL, MAILTRAP_SANDBOX_ID, MAILTRAP_TEST_INBOX_ID, MAILTRAP_ORGANIZATION_ID, MAILTRAP_ORGANIZATION_API_TOKEN.
  • You want tools like send-email, batch-send-transactional-email, batch-send-bulk-email.
Explore Mailtrap

Email MCP logoChoose Email MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You want tools like email_list_accounts, email_add_account, email_remove_account.
Explore Email MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMailtrap logoMailtrapEmail MCP logoEmail MCP
CategoryCommunicationCommunication
Quality signal64/100 · Good68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredother
PricingNot declaredFree
Required env varsMAILTRAP_API_TOKENMAILTRAP_ACCOUNT_IDDEFAULT_FROM_EMAILMAILTRAP_SANDBOX_IDMAILTRAP_TEST_INBOX_IDMAILTRAP_ORGANIZATION_IDMAILTRAP_ORGANIZATION_API_TOKENNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars6626
Directory activity 0 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
Tools12533

Tools & capabilities

Mailtrap tools 125

  • send-emailSend an email to your recipient email address using Mailtrap Email API. You can send emails to multiple recipients at once.
  • batch-send-transactional-emailSend a batch of transactional emails in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include `to`.
  • batch-send-bulk-emailSend a batch of bulk emails (Mailtrap bulk-stream API) in one call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Each request must include at least one of `to`/`cc`/`bcc`.
  • create-templateCreate a new email template
  • list-templatesList the account's email templates with page-token pagination (`token`, `per_page`). Pages are offsets over the newest-first list, so after deleting templates list again from token 1 instead of continuing with the next token.
  • get-templateGet a single email template by ID, including subject, category, and HTML/text body.
  • update-templateUpdate an existing email template
  • delete-templateDelete an existing email template
  • send-sandbox-emailSend an email in sandbox mode to a test inbox without delivering to your recipients
  • batch-send-sandbox-emailSend a batch of emails in sandbox mode to a test inbox in one Mailtrap API call. Shared fields go on `base`; per-recipient overrides go in `requests[]`. Requires `sandbox_id` or the MAILTRAP_SANDBOX_ID env var.
  • get-sandbox-messagesGet list of messages from the sandbox test inbox
  • show-sandbox-email-messageShow sandbox email message details and content from the sandbox test inbox. Optionally include spam report (SpamAssassin score) and HTML analysis (client compatibility) for email testing workflows.
  • +113 more on the listing page

Email MCP tools 33

  • email_list_accountsList all configured email accounts and their connection status
  • email_add_accountAdd a new IMAP or iCloud email account (Gmail and Outlook require the setup wizard for OAuth)
  • email_remove_accountRemove an email account: deletes its stored credentials, revokes the Google grant for Gmail accounts, and removes Outlook tokens from the local token cache. The result reports whether provider-side revocation succeeded.
  • email_test_accountTest an email account connection
  • email_list_foldersList all email folders for an account
  • email_searchSearch emails with filters. By default returns compact results without full body content to save context. Set returnBody=true to include full email bodies.
  • email_getGet a single email by ID
  • email_get_threadGet an email thread by thread ID
  • email_get_attachmentGet an email attachment by ID, returns base64 encoded data
  • email_save_attachmentDownload an email attachment and save it directly to disk, returning metadata only (no base64 in the response) — avoids paying the token cost of round-tripping large attachments through the calling model. outputPath is relative to a fixed downloads directory (/home/user/.email-mcp/downloads, override with EMAIL_MCP_DOWNLOADS_DIR) and cannot escape it.
  • email_sendSend a new email
  • email_replyReply to an existing email
  • +21 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Mailtrap

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mailtrap": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-mailtrap"
      ],
      "env": {
        "MAILTRAP_API_TOKEN": "YOUR_MAILTRAP_API_TOKEN_HERE",
        "MAILTRAP_ACCOUNT_ID": "YOUR_MAILTRAP_ACCOUNT_ID_HERE",
        "DEFAULT_FROM_EMAIL": "YOUR_DEFAULT_FROM_EMAIL_HERE",
        "MAILTRAP_SANDBOX_ID": "YOUR_MAILTRAP_SANDBOX_ID_HERE",
        "MAILTRAP_TEST_INBOX_ID": "YOUR_MAILTRAP_TEST_INBOX_ID_HERE",
        "MAILTRAP_ORGANIZATION_ID": "YOUR_MAILTRAP_ORGANIZATION_ID_HERE",
        "MAILTRAP_ORGANIZATION_API_TOKEN": "YOUR_MAILTRAP_ORGANIZATION_API_TOKEN_HERE"
      }
    }
  }
}

Email MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "marlinjai-email-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@marlinjai/email-mcp"
      ]
    }
  }
}

Frequently asked questions

Mailtrap is categorized under Communication and uses a local stdio subprocess. Email MCP belongs to Communication and uses a local stdio subprocess. Pick Mailtrap for communication work and Email MCP for communication.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Mailtrap has no declared pricing — check the project's own site. Email MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mailtrap and marlinjai-email-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Mailtrap has a quality signal of 64/100 (Good) with 0 views, 0 installs and 66 GitHub stars. Email MCP has 68/100 (Great) with 8 views, 0 installs and 26 GitHub stars.