Ext Ops Panel
Open dashboard
Comparison

@cocal/google-calendar-mcp vs Postman MCP Server

@cocal/google-calendar-mcp is an MCP server published by @cocal. Marketplaces we read that list it: 1 (npm registry (MCP servers)). 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)). As of our marketplace pass on 2026-10-30. 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

Where each is published
Marketplace@cocal/google-calendar-mcpPostman MCP Server
npm registry (MCP servers) Listed
Version: 2.8.1
Downloads/month (npm): 36 840
Downloads/week (npm): 9 959
Forks (GitHub): 336
Stars (GitHub): 1 206
Not marked · First seen
Listed
Version: 2.15.0
Downloads/month (npm): 33 131
Downloads/week (npm): 7 080
Forks (GitHub): 88
Stars (GitHub): 325
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 2.15.0
Downloads/month (npm): 33 131
Downloads/week (npm): 7 080
Forks (GitHub): 88
Stars (GitHub): 325
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:73f715030cbe
Forks (GitHub): 88
Pulls (Docker Hub): 46 585
Stars (Docker Hub): 6
Stars (GitHub): 325
Not marked · First seen

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

@cocal/google-calendar-mcp vs Postman MCP Server
Fact@cocal/google-calendar-mcpPostman MCP Server
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)1 206 (better)325 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub46 585
Forks (GitHub) (differs)336 (better)88 (worse)
Last release (differs)2026-10-30 (worse)2026-10-30 (better)
Where it runs (differs)On your machine (@cocal/google-calendar-mcp)Remote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published42
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITApache-2.0
Repository (differs)github.com/nspady/google-calendar-mcpgithub.com/postmanlabs/postman-mcp-server
Changes in the last 7 days22
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 7 days ago, requires a key

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

@cocal/google-calendar-mcp

In its own words, on npm registry (MCP servers):

Google Calendar MCP Server with extensive support for calendar management

Postman MCP Server

In its own words, on Official MCP Registry:

Give your AI agents trusted access to the full Postman platform.

How to run each

@cocal/google-calendar-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Postman MCP Server As a remote MCP server

Claude Code
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

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 @cocal/google-calendar-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of @cocal/google-calendar-mcp publish no settings it asks for, so we do not compare settings.

What it can do: @cocal/google-calendar-mcp · What it can do: Postman MCP Server · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built