Gmail vs Imap MCP Server
A side-by-side look at the Gmail and Imap MCP Server 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 Imap MCP Server 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 Imap MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
imap_add_account, imap_update_account, imap_list_accounts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 48/100 · Fair | 71/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRETMCP_TRANSPORTPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12 | 111 |
| Directory activity | 3 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 43 | 40 |
| Full listing | View Gmail | View Imap MCP Server |
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
Imap MCP Server tools 40
imap_add_accountAdd a new IMAP account configurationimap_update_accountUpdate an existing IMAP account. Useful for fixing SMTP settings without removing and re-adding the account.imap_list_accountsList all configured IMAP accountsimap_remove_accountRemove an IMAP account configurationimap_connectConnect to an IMAP accountimap_disconnectDisconnect from an IMAP accountimap_test_accountTest an existing account connection without re-entering credentials. Validates IMAP connectivity and returns folder count and message count.imap_search_emailsNote: on some servers a 'flagged' or starred message carries a custom keyword (e.g. an Open-Xchange color label or Apple's $MailFlagBit*) instead of, or in addition to, the \Flagged system flag. After any flagged search, inspect each result's customKeywords field before concluding a message is or isn't flagged — do not rely on the flagged filter alone. Search for emails matching criteria (sender, recipient, subject, body text, date range, read/flagged status). Use this to FIND messages when you know something about them but not their UID — e.g. "emails from amazon last week", "unread invoices". By default searches a single folder (INBOX). Set searchAllFolders=true to scan every mailbox at once — this catches messages filed away by rules (e.g. a receipt routed to a custom folder); Trash/Spam/Drafts are skipped unless you opt in. By default returns lightweight headers (uid, from, subject, date, and folder when searching across folders); set `includeBody=true` to also return the parsed body in one round-trip instead of paying the N+1 cost of calling imap_get_email per match. For the newest messages without criteria, prefer imap_get_latest_emails.imap_get_emailRead the FULL content of a single email by its UID (body, sender/recipients, date, attachment list, optional raw headers and text-attachment previews). By default the body is returned as clean Markdown in markdownContent and raw HTML is omitted so it never crosses the boundary; set bodyFormat to "html" for the legacy raw htmlContent, or "text" for plain text only. Use after imap_search_emails or imap_get_latest_emails gives you a uid. Body text is truncated to maxContentLength to protect the context window — raise it for long messages. To fetch attachment bytes, use imap_download_attachment.imap_upload_fileUpload a file to the server for use as an email attachment. Returns a path that can be used with imap_send_email attachments. This allows sending large attachments without hitting context window limits. Max size: 26214400 bytes (configurable via IMAP_MAX_UPLOAD_SIZE). Uploads are auto-deleted after 86400000 ms (configurable via IMAP_UPLOAD_TTL_MS).imap_download_attachmentDownload a single attachment from an email (folder + uid + attachment filename/contentId, as listed by imap_get_email). Images are returned inline for viewing; PDFs are saved and their text is extracted inline (extractText); other files are saved to the shared downloads directory (or savePath). Use when the user wants the actual file contents, not just the message body.imap_mark_as_readMark one or many emails as read. Accepts a single UID or an array — pass an array to flag N messages in one IMAP STORE round-trip (useful when triaging).- +28 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.
Imap MCP Server
{
"mcpServers": {
"imap-mcp-server": {
"command": "npx",
"args": [
"-y",
"imap-mcp-server"
]
}
}
}
Frequently asked questions
Gmail is categorized under Communication and uses an install path we have not confirmed yet. Imap MCP Server belongs to Communication and uses a local stdio subprocess. Pick Gmail for communication work and Imap MCP Server 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. Imap MCP Server is listed as free. Auth: other. 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 imap-mcp-server 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. Imap MCP Server has 71/100 (Great) with 8 views, 0 installs and 111 GitHub stars.