Gmail vs Gmail MCP
A side-by-side look at the Gmail and Gmail MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gmail for communication work; choose Gmail 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?
Choose 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.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 48/100 · Fair | 57/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRETMCP_TRANSPORTPORT | GMAIL_MCP_RECIPIENT_PAIRING |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12 | 15 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 43 | Not listed |
| Full listing | View Gmail | View Gmail MCP |
Tools & capabilities
Gmail tools 43
gmail_get_profileGet user's email address and profile infoMessagesgmail_messages_listSearch/list messages (consider `gmail_threads_list` instead)gmail_message_getGet a single messagegmail_message_sendSend an emailgmail_message_forwardForward an email to new recipientsgmail_message_modifyAdd/remove labelsgmail_message_archiveArchive (remove from inbox)gmail_message_trashMove to trashgmail_message_untrashRestore from trashgmail_message_deletePermanently deletegmail_messages_batch_modifyBulk label changes- +31 more on the listing page
Gmail MCP 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
No confirmed install command for Gmail yet — follow the setup steps linked from its listing page rather than a guessed package name.
Gmail MCP
{
"mcpServers": {
"klodr-gmail-mcp": {
"command": "npx",
"args": [
"-y",
"@klodr/gmail-mcp"
],
"env": {
"GMAIL_MCP_RECIPIENT_PAIRING": "YOUR_GMAIL_MCP_RECIPIENT_PAIRING_HERE"
}
}
}
}
Frequently asked questions
Gmail is categorized under Communication and uses an install path we have not confirmed yet. Gmail MCP belongs to Communication and uses a local stdio subprocess. Pick Gmail for communication work and Gmail 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 has no confirmed install command yet — follow its own setup instructions.
Gmail has no declared pricing — check the project's own site. Gmail MCP is listed as free. Auth: oauth 2.0. 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 klodr-gmail-mcp 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. Gmail MCP has 57/100 (Good) with 3 views, 0 installs and 15 GitHub stars.