Ext Ops Panel
Open dashboard
Comparison

Filesystem (Reference) vs Proton Drive CLI MCP

Filesystem (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Proton Drive CLI MCP is an MCP server published by borealstack. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
MarketplaceFilesystem (Reference)Proton Drive CLI MCP
Docker MCP Catalog Listed
Version: sha256:35fcf0217ca0
Forks (GitHub): 11 780
Pulls (Docker Hub): 288 522
Stars (Docker Hub): 28
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 261
Downloads/week (npm): 42
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

Filesystem (Reference) vs Proton Drive CLI MCP
FactFilesystem (Reference)Proton Drive CLI MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 180 (better)0 (worse)
Pulls (Docker Hub) (differs)288 522No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/filesystem)On your machine (@borealstack/proton-drive-cli-mcp)
Transportstdiostdio
Tools it declares (differs)11Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/borealstack/proton-drive-cli-mcp
Changes in the last 7 days (differs)02
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

Filesystem (Reference)

In its own words, on Docker MCP Catalog:

Local filesystem access with configurable allowed paths.

Proton Drive CLI MCP

In its own words, on Official MCP Registry:

Manage Proton Drive from MCP clients through Proton's official CLI without exposing credentials.

How to run each

Filesystem (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio filesystem -- docker run -i --rm mcp/filesystem

Proton Drive CLI MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio proton-drive-cli-mcp -- npx -y @borealstack/proton-drive-cli-mcp

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

Tools each declares

The marketplaces of Proton Drive CLI MCP publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Filesystem (Reference) · What it can do: Proton Drive CLI 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. Data comes from public marketplace files in GitHub repositories of their authors. 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