Compared · gmail
16 Gmail MCP servers. Which one to use.
Every Gmail server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 16 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Gmail | io.github.domdomegg | no flag | REVIEW | 95 | npm gmail-mcp |
| Gmail Postmaster Tools | io.github.optipub | no flag | REVIEW | 90 | not published |
| io.github.ArtyMcLabin/Gmail-MCP-Server | io.github.ArtyMcLabin | no flag | REVIEW | 85 | npm @artymclabin/gmail-mcp |
| Multi-Account Gmail | io.github.cunicopia-dev | no flag | REVIEW | 84 | pypi multi-account-gmail-mcp |
| com.mcparmory/google-gmail | com.mcparmory | no flag | REVIEW | 80 | pypi mcparmory-google-gmail |
| io.github.gx-55/multi-gmail-mcp | io.github.gx-55 | no flag | REVIEW | 79 | npm multi-gmail-mcp |
| Gmail | io.github.pipeworx-io | no flag | REVIEW | 79 | remote endpoint |
| com.pulsemcp/gmail | com.pulsemcp | no flag | REVIEW | 78 | npm gmail-workspace-mcp-server |
| io.github.zayansalman/gmail-attachments-mcp | io.github.zayansalman | no flag | REVIEW | 78 | pypi gmail-attachments-mcp |
| io.github.markswendsen-code/gmail | io.github.markswendsen-code | no flag | REVIEW | 71 | npm @striderlabs/mcp-gmail |
| Gmail | io.github.mcp-z | no flag | REVIEW | 71 | npm @mcp-z/mcp-gmail |
| ai.smithery/sebastianall1977-gmail-mcp | ai.smithery | no flag | REVIEW | 63 | remote endpoint |
| ai.smithery/faithk7-gmail-mcp | ai.smithery | no flag | REVIEW | 62 | remote endpoint |
| com.mintmcp/gmail | com.mintmcp | no flag | REVIEW | 62 | remote endpoint |
| io.github.mkpoli/gmail-mcp | io.github.mkpoli | no flag | not screened | 60 | not published |
| ai.waystation/gmail | ai.waystation | no flag | REVIEW | 57 | remote endpoint |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.