Gmail vs Mailtrap

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

Gmail logoGmailCommunicationAllow AI systems to read, send, archive, and manage emails via Gmail.48FairAuth: not declaredMailtrap logoMailtrapCommunication · Local subprocess (stdio)Official mailtrap.io MCP server64GoodAuth: not declared

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

Which MCP server should you choose?

Gmail logoChoose Gmail when

  • You need dedicated capabilities in the Communication domain.
  • You have the keys it needs: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, MCP_TRANSPORT, PORT.
  • You want tools like gmail_get_profile, Messages, gmail_messages_list.
Explore Gmail

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGmail logoGmailMailtrap logoMailtrap
CategoryCommunicationCommunication
Quality signal48/100 · Fair64/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsGOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRETMCP_TRANSPORTPORTMAILTRAP_API_TOKENMAILTRAP_ACCOUNT_IDDEFAULT_FROM_EMAILMAILTRAP_SANDBOX_IDMAILTRAP_TEST_INBOX_IDMAILTRAP_ORGANIZATION_IDMAILTRAP_ORGANIZATION_API_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars1266
Directory activity 3 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools43125

Tools & capabilities

Gmail tools 43

  • gmail_get_profileGet user's email address and profile info
  • Messages
  • gmail_messages_listSearch/list messages (consider `gmail_threads_list` instead)
  • gmail_message_getGet a single message
  • gmail_message_sendSend an email
  • gmail_message_forwardForward an email to new recipients
  • gmail_message_modifyAdd/remove labels
  • gmail_message_archiveArchive (remove from inbox)
  • gmail_message_trashMove to trash
  • gmail_message_untrashRestore from trash
  • gmail_message_deletePermanently delete
  • gmail_messages_batch_modifyBulk label changes
  • +31 more on the listing page

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

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.

Gmail

No confirmed install command for Gmail yet — follow the setup steps linked from its listing page rather than a guessed package name.

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

Frequently asked questions

Gmail is categorized under Communication and uses an install path we have not confirmed yet. Mailtrap belongs to Communication and uses a local stdio subprocess. Pick Gmail for communication work and Mailtrap 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. Gmail has no confirmed install command yet — follow its own setup instructions.

Gmail has no declared pricing — check the project's own site. Mailtrap has no declared pricing — check the project's own site. 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 gmail and mailtrap as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Gmail has a quality signal of 48/100 (Fair) with 3 views, 0 installs and 12 GitHub stars. Mailtrap has 64/100 (Good) with 3 views, 0 installs and 66 GitHub stars.