Mailtrap vs Jmap MCP

A side-by-side look at the Mailtrap and Jmap 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 declaredJmap MCP logoJmap MCPCommunication · Remote HTTP/SSEA Model Context Protocol (MCP) server that provides tools for interacting with JMAP (JSON Meta Application Protocol) email servers. Built with Deno and using the jmap-jam client library.60GoodAuth: api key required

Verdict: choose Mailtrap for communication work as a local process; choose Jmap MCP for communication over a hosted endpoint. 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

Jmap MCP logoChoose Jmap MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: JMAP_SESSION_URL, JMAP_BEARER_TOKEN.
  • You want tools like get_mailboxes, search_emails, get_emails.
Explore Jmap MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMailtrap logoMailtrapJmap MCP logoJmap MCP
CategoryCommunicationCommunication
Quality signal64/100 · Good60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsMAILTRAP_API_TOKENMAILTRAP_ACCOUNT_IDDEFAULT_FROM_EMAILMAILTRAP_SANDBOX_IDMAILTRAP_TEST_INBOX_IDMAILTRAP_ORGANIZATION_IDMAILTRAP_ORGANIZATION_API_TOKENJMAP_SESSION_URLJMAP_BEARER_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars66178
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools12512

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

Jmap MCP tools 12

  • get_mailboxesList mailboxes/folders with their IDs, names, and metadata. **Call this first**
  • search_emailsSearch emails with filters. **All filters are AND'd together.** Returns only
  • get_emailsRetrieve specific emails by their IDs. Use `properties` to request only what you
  • get_threadsGet email threads by their IDs. Thread IDs come from `get_emails` responses
  • get_email_changesGet IDs of emails created, updated, or destroyed since a previous state. Use the
  • get_search_updatesGet changes within a previous search query since its `queryState`. Must use the
  • mark_emailsMark emails as read/unread or flagged/unflagged.
  • move_emailsMove emails to a different mailbox. Use `get_mailboxes` to find the target
  • patch_email_mailboxesAdd or remove selected mailbox memberships without replacing unspecified
  • delete_emailsDelete emails permanently (cannot be undone). Prefer moving to Trash via
  • send_emailSend a new email. Requires either `textBody` or `htmlBody` (or both).
  • reply_to_emailReply to an existing email. Automatically sets To/CC, Re: subject prefix, and

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"
      }
    }
  }
}

Jmap MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wyattjoh-jmap-mcp": {
      "url": "https://api.fastmail.com/jmap/session"
    }
  }
}

Frequently asked questions

Mailtrap is categorized under Communication and uses a local stdio subprocess. Jmap MCP belongs to Communication and uses a remote HTTP/SSE transport. Pick Mailtrap for communication work and Jmap 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. Jmap MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 wyattjoh-jmap-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. Jmap MCP has 60/100 (Good) with 2 views, 0 installs and 178 GitHub stars.