Gmail MCP vs Jmap MCP

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

Gmail MCP logoGmail MCPCommunication · Local subprocess (stdio)Gmail MCP server — scope-gated tools + attachment/download path jails + supply-chain hardening. Fork of GongRzhe/Gmail-MCP-Server via ArtyMcLabin's intermediate fork.57GoodAuth: oauth 2.0Jmap 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.61GoodAuth: api key required

Verdict: choose Gmail MCP 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?

Gmail MCP logoChoose Gmail MCP when

  • You need dedicated capabilities in the Communication domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You have the keys it needs: GMAIL_MCP_RECIPIENT_PAIRING.
Explore Gmail MCP

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.

SpecGmail MCP logoGmail MCPJmap MCP logoJmap MCP
CategoryCommunicationCommunication
Quality signal57/100 · Good61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthOAuth 2.0API key required
PricingFreeBYOK (pay the provider)
Required env varsGMAIL_MCP_RECIPIENT_PAIRINGJMAP_SESSION_URLJMAP_BEARER_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars15178
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed12

Tools & capabilities

Gmail MCP tools

No tool names declared yet. Check the project README from 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.

Gmail MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "klodr-gmail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@klodr/gmail-mcp"
      ],
      "env": {
        "GMAIL_MCP_RECIPIENT_PAIRING": "YOUR_GMAIL_MCP_RECIPIENT_PAIRING_HERE"
      }
    }
  }
}

Jmap MCP

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

Frequently asked questions

Gmail MCP is categorized under Communication and uses a local stdio subprocess. Jmap MCP belongs to Communication and uses a remote HTTP/SSE transport. Pick Gmail MCP 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.

Gmail MCP is listed as free. Auth: oauth 2.0. 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 klodr-gmail-mcp and wyattjoh-jmap-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Gmail MCP has a quality signal of 57/100 (Good) with 1 views, 0 installs and 15 GitHub stars. Jmap MCP has 61/100 (Good) with 2 views, 0 installs and 178 GitHub stars.