Postman MCP Server vs com.pulsemcp/gmail
Postman MCP Server is an MCP server published by postman.com. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, npm registry (MCP servers)). com.pulsemcp/gmail is an MCP server published by pulsemcp.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Postman MCP Server |  com.pulsemcp/gmail |
|---|---|---|
| Official MCP Registry | Listed Version: 2.14.0 Downloads/month (npm): 33 131 Downloads/week (npm): 7 080 Forks (GitHub): 88 Stars (GitHub): 325 Not marked · First seen |
Listed Version: 0.4.12 Downloads/month (npm): 446 Downloads/week (npm): 33 Forks (GitHub): 10 Stars (GitHub): 81 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:73f715030cbe Forks (GitHub): 88 Pulls (Docker Hub): 46 494 Stars (Docker Hub): 6 Stars (GitHub): 325 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 2.14.0 Downloads/month (npm): 33 131 Downloads/week (npm): 7 080 Forks (GitHub): 88 Stars (GitHub): 325 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Postman MCP Server | com.pulsemcp/gmail |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 325 (better) | 81 (worse) |
| Pulls (Docker Hub) (differs) | 46 494 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 88 (better) | 10 (worse) |
| Last release (differs) | 2026-10-16 | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (gmail-workspace-mcp-server) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 7, secrets among them: 4 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/postmanlabs/postman-mcp-server | github.com/pulsemcp/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Postman MCP Server
Give your AI agents trusted access to the full Postman platform.
com.pulsemcp/gmail
MCP server for Gmail with OAuth2 (personal) and service account (Workspace) support.
How to run each
Postman MCP Server As a remote MCP server
claude mcp add --transport http postman-mcp-server https://mcp.postman.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: POSTMAN_API_KEY (secret), Authorization header
com.pulsemcp/gmail As a local MCP server: npm package
claude mcp add --env "GMAIL_OAUTH_CLIENT_ID=<YOUR_GMAIL_OAUTH_CLIENT_ID>" --env "GMAIL_OAUTH_CLIENT_SECRET=<YOUR_GMAIL_OAUTH_CLIENT_SECRET>" --env "GMAIL_OAUTH_REFRESH_TOKEN=<YOUR_GMAIL_OAUTH_REFRESH_TOKEN>" --env "GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY=<YOUR_GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY>" --transport stdio gmail -- npx -y gmail-workspace-mcp-serverRequires: GMAIL_OAUTH_CLIENT_ID (secret), GMAIL_OAUTH_CLIENT_SECRET (secret), GMAIL_OAUTH_REFRESH_TOKEN (secret), GMAIL_SERVICE_ACCOUNT_PRIVATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Postman MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of com.pulsemcp/gmail publish no list of tools, so we do not compare tools.
Settings each asks for
Only Postman MCP Server asks for
POSTMAN_API_KEY (secret)
Only com.pulsemcp/gmail asks for
GMAIL_ENABLED_TOOLGROUPSGMAIL_IMPERSONATE_EMAILGMAIL_OAUTH_CLIENT_ID (secret)GMAIL_OAUTH_CLIENT_SECRET (secret)GMAIL_OAUTH_REFRESH_TOKEN (secret)GMAIL_SERVICE_ACCOUNT_CLIENT_EMAILGMAIL_SERVICE_ACCOUNT_PRIVATE_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Postman MCP Server · What it can do: com.pulsemcp/gmail · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.