Gmail MCP vs Mailbox

A side-by-side look at the Gmail MCP and Mailbox 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.0
M
MailboxCommunication
Physical mail API for AI agents. Send letters, certified mail, postcards from code via MCP.37FairAuth: not declared

Verdict: choose Gmail MCP for communication work as a local process; choose Mailbox for communication. 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

M
Choose Mailbox when

  • You need dedicated capabilities in the Communication domain.
Explore Mailbox

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGmail MCP logoGmail MCP
M
Mailbox
CategoryCommunicationCommunication
Quality signal57/100 · Good37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthOAuth 2.0Not declared
PricingFreeNot declared
Required env varsGMAIL_MCP_RECIPIENT_PAIRINGNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars15—
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Gmail MCP tools

No tool names declared yet. Check the project README from the listing page.

Mailbox tools

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

Mailbox

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

Frequently asked questions

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

Gmail MCP is listed as free. Auth: oauth 2.0. Mailbox 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 klodr-gmail-mcp and mailbox 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 2 views, 0 installs and 15 GitHub stars. Mailbox has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.