Ext Ops Panel
Open dashboard
Comparison

AWS Core vs io.github.IceyWu/icloud-calendar

AWS Core is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.IceyWu/icloud-calendar is an MCP server published by IceyWu. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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

Where each is published
MarketplaceAWS Coreio.github.IceyWu/icloud-calendar
Docker MCP Catalog Listed
Version: sha256:f624682618e2
Forks (GitHub): 1 835
Pulls (Docker Hub): 131 913
Stars (Docker Hub): 3
Stars (GitHub): 9 839
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.3
Downloads/month (npm): 1 238
Downloads/week (npm): 202
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.1.3
Downloads/month (npm): 1 238
Downloads/week (npm): 202
Forks (GitHub): 0
Stars (GitHub): 0
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

AWS Core vs io.github.IceyWu/icloud-calendar
FactAWS Coreio.github.IceyWu/icloud-calendar
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)9 839 (better)0 (worse)
Pulls (Docker Hub) (differs)131 913No figure on Docker Hub
Forks (GitHub) (differs)1 835 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/aws-core-mcp-server)On your machine (icloud-calendar-mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/awslabs/mcpgithub.com/iceywu/icloud-calendar-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

AWS Core

In its own words, on Docker MCP Catalog:

Starting point for using the awslabs MCP servers.

io.github.IceyWu/icloud-calendar

In its own words, on Official MCP Registry:

Manage Apple iCloud Calendar through a reliable CalDAV MCP server.

How to run each

AWS Core As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-core-mcp-server -- docker run -i --rm mcp/aws-core-mcp-server

io.github.IceyWu/icloud-calendar As a local MCP server: npm package

Claude Code
claude mcp add --env "ICLOUD_APP_PASSWORD=<YOUR_ICLOUD_APP_PASSWORD>" --env "ICLOUD_USERNAME=<YOUR_ICLOUD_USERNAME>" --transport stdio icloud-calendar -- npx -y icloud-calendar-mcp

Requires: ICLOUD_APP_PASSWORD (secret), ICLOUD_USERNAME

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of io.github.IceyWu/icloud-calendar publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of AWS Core publish no settings it asks for, so we do not compare settings.

What it can do: AWS Core · What it can do: io.github.IceyWu/icloud-calendar · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.

Where the data comes from: how the catalog is built