Mailtrap vs Nestr MCP

A side-by-side look at the Mailtrap and Nestr 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 declaredNestr MCP logoNestr MCPCommunication · Local subprocess (stdio)Connect AI to Nestr for Holacracy, Sociocracy, and self-organizing teams.60GoodAuth: api key required

Verdict: choose Mailtrap for communication work as a local process; choose Nestr 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

Nestr MCP logoChoose Nestr MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: NESTR_API_KEY, NESTR_OAUTH_TOKEN.
  • You want tools like nestr_list_workspaces, nestr_get_workspace, nestr_create_workspace.
Explore Nestr MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMailtrap logoMailtrapNestr MCP logoNestr MCP
CategoryCommunicationCommunication
Quality signal64/100 · Good60/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredNot declared
Required env varsMAILTRAP_API_TOKENMAILTRAP_ACCOUNT_IDDEFAULT_FROM_EMAILMAILTRAP_SANDBOX_IDMAILTRAP_TEST_INBOX_IDMAILTRAP_ORGANIZATION_IDMAILTRAP_ORGANIZATION_API_TOKENNESTR_API_KEYNESTR_OAUTH_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars666
Directory activity 3 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools12569

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

Nestr MCP tools 69

  • nestr_list_workspacesList accessible workspaces
  • nestr_get_workspaceGet workspace details
  • nestr_create_workspaceCreate a new workspace (OAuth only)
  • nestr_searchSearch for nests (tasks, projects, roles)
  • nestr_get_meGet current user identity and workspace list
  • nestr_get_nestGet details of a specific nest (supports batch fetch with comma-separated IDs; single-nest `provenance`/`rights`/`whoCan` flags available)
  • nestr_explain_nestDiagnose one nest: field/property provenance (which label/circle defines each), the caller's composed rights with a deny trace, and (with `whoCan`) who can act on it and who to contact
  • nestr_get_nest_childrenGet child nests
  • nestr_create_nestCreate a new nest
  • nestr_update_nestUpdate nest properties
  • nestr_delete_nestDelete a nest
  • nestr_reorder_nestReorder a nest relative to another
  • +57 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"
      }
    }
  }
}

Nestr MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-348": {
      "command": "npx",
      "args": [
        "-y",
        "@nestr/mcp"
      ],
      "env": {
        "NESTR_API_KEY": "YOUR_NESTR_API_KEY_HERE",
        "NESTR_OAUTH_TOKEN": "YOUR_NESTR_OAUTH_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

Mailtrap is categorized under Communication and uses a local stdio subprocess. Nestr MCP belongs to Communication and uses a local stdio subprocess. Pick Mailtrap for communication work and Nestr 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. Nestr MCP has no declared pricing — check the project's own site. 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 mcp-348 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 3 views, 0 installs and 66 GitHub stars. Nestr MCP has 60/100 (Good) with 0 views, 0 installs and 6 GitHub stars.