Ext Ops Panel
Open dashboard
Comparison

VeyraX vs CalDAV MCP Server

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). CalDAV MCP Server is an MCP server published by lukegskw. 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

Where each is published
MarketplaceVeyraXCalDAV MCP Server
Docker MCP Catalog Listed
Version: sha256:257d91533072
Forks (GitHub): 19
Pulls (Docker Hub): 18 743
Stars (Docker Hub): 4
Stars (GitHub): 48
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Forks (GitHub): 3
Stars (GitHub): 5
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

VeyraX vs CalDAV MCP Server
FactVeyraXCalDAV MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)48 (better)5 (worse)
Pulls (Docker Hub) (differs)18 743No figure on Docker Hub
Forks (GitHub) (differs)19 (better)3 (worse)
Last release (differs)Not published2026-10-21
Where it runs (differs)On your machine (mcp/veyrax)On your machine (ghcr.io/lukegskw/caldav-mcp:0.2.0)
Transportstdiostdio
Tools it declares (differs)3Not published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/veyrax/veyrax-mcpgithub.com/lukegskw/caldav-mcp
Changes in the last 7 days (differs)42
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

VeyraX

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

CalDAV MCP Server

In its own words, on Official MCP Registry:

A TypeScript MCP server for iCloud Calendar with native multi-VALARM support.

How to run each

VeyraX As a local MCP server: Docker image

Claude Code
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyrax

Requires: VEYRAX_API_KEY (secret)

CalDAV MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --env "CALDAV_PASSWORD=<YOUR_CALDAV_PASSWORD>" --env "CALDAV_USERNAME=<YOUR_CALDAV_USERNAME>" --transport stdio caldav-mcp -- docker run -i --rm -e CALDAV_PASSWORD -e CALDAV_USERNAME ghcr.io/lukegskw/caldav-mcp:0.2.0

Requires: CALDAV_PASSWORD (secret), CALDAV_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 CalDAV MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Only VeyraX asks for

  • VEYRAX_API_KEY (secret)

Only CalDAV MCP Server asks for

  • CALDAV_PASSWORD (secret)
  • CALDAV_USERNAME

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: VeyraX · What it can do: CalDAV MCP Server · 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. 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