Ext Ops Panel
Open dashboard
Comparison

Close vs io.github.PhilflowIO/dav-mcp

Close is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.PhilflowIO/dav-mcp is an MCP server published by PhilflowIO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceCloseio.github.PhilflowIO/dav-mcp
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 5.0.0
Downloads/month (npm): 2 278
Downloads/week (npm): 1 086
Forks (GitHub): 16
Stars (GitHub): 40
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

Close vs io.github.PhilflowIO/dav-mcp
FactCloseio.github.PhilflowIO/dav-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub40
Forks (GitHub) (differs)No figure on GitHub16
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.close.com/mcp)On your machine (dav-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 110, secrets among them: 3
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/philflowio/dav-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

Close

In its own words, on Docker MCP Catalog:

Streamline sales processes with integrated calling, email, SMS, and automated workflows for small and scaling businesses.

io.github.PhilflowIO/dav-mcp

In its own words, on Official MCP Registry:

AI-orchestrated calendars, contacts & tasks across any DAV platform. 27 tools, field-agnostic.

How to run each

Close As a remote MCP server

Claude Code
claude mcp add --transport http close https://mcp.close.com/mcp

Requires: CLOSE_API_KEY (secret)

io.github.PhilflowIO/dav-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "CALDAV_PASSWORD=<YOUR_CALDAV_PASSWORD>" --env "CALDAV_SERVER_URL=<YOUR_CALDAV_SERVER_URL>" --env "CALDAV_USERNAME=<YOUR_CALDAV_USERNAME>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GOOGLE_REFRESH_TOKEN=<YOUR_GOOGLE_REFRESH_TOKEN>" --transport stdio dav-mcp -- npx -y dav-mcp

Requires: CALDAV_PASSWORD (secret), CALDAV_SERVER_URL, CALDAV_USERNAME, GOOGLE_CLIENT_SECRET (secret), GOOGLE_REFRESH_TOKEN (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Close asks for

  • CLOSE_API_KEY (secret)

Only io.github.PhilflowIO/dav-mcp asks for

  • AUTH_METHOD
  • CALDAV_PASSWORD (secret)
  • CALDAV_SERVER_URL
  • CALDAV_USERNAME
  • GOOGLE_CLIENT_ID
  • GOOGLE_CLIENT_SECRET (secret)
  • GOOGLE_REFRESH_TOKEN (secret)
  • GOOGLE_SERVER_URL
  • GOOGLE_TOKEN_URL
  • GOOGLE_USER

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

What it can do: Close · What it can do: io.github.PhilflowIO/dav-mcp · 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