Postman MCP Server vs Calensync
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)). Calensync is an MCP server published by calensync.live. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. 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 |  Calensync |
|---|---|---|
| Official MCP Registry | Listed Version: 2.15.0 Downloads/month (npm): 46 496 Downloads/week (npm): 7 759 Forks (GitHub): 86 Stars (GitHub): 328 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:73f715030cbe Forks (GitHub): 86 Pulls (Docker Hub): 47 569 Stars (Docker Hub): 6 Stars (GitHub): 328 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 2.15.0 Downloads/month (npm): 46 496 Downloads/week (npm): 7 759 Forks (GitHub): 86 Stars (GitHub): 328 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 | Calensync |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 328 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 47 569 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 86 | No figure on GitHub |
| Last release (differs) | 2026-10-30 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (api.calensync.live/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/postmanlabs/postman-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 8 h ago, requires authentication | Answered with HTTP 307 (12 h ago) |
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.
Calensync
Manage Google, Outlook & Apple calendars and create private sync rules from chat.
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
Calensync As a remote MCP server
claude mcp add --transport http calensync https://api.calensync.live/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of Postman MCP Server responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of Calensync publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Calensync publish no settings it asks for, so we do not compare settings.
What it can do: Postman MCP Server · What it can do: Calensync · 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.