Ext Ops Panel
Open dashboard
Comparison

Filesystem (Reference) vs egnyte

Filesystem (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). egnyte is a plugin bundle for AI coding tools published by egnyte. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-14. 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)egnyte
Docker MCP Catalog Listed
Version: sha256:35fcf0217ca0
Forks (GitHub): 11 787
Pulls (Docker Hub): 289 574
Stars (Docker Hub): 28
Stars (GitHub): 91 222
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 2
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 egnyte
FactFilesystem (Reference)egnyte
Marketplaces that list it11
Stars (GitHub) (differs)91 222 (better)2 (worse)
Pulls (Docker Hub) (differs)289 574No figure on Docker Hub
Forks (GitHub) (differs)11 787 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/filesystem)Remote server (mcp-server.egnyte.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)11Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle3
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/egnyte/egnyte-for-ai
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

Filesystem (Reference)

In its own words, on Docker MCP Catalog:

Local filesystem access with configurable allowed paths.

egnyte

In its own words, on Claude Code: claude-plugins-community:

Search, manage, and extract intelligence from Egnyte enterprise content. Connects Claude Code to your Egnyte domain via the Egnyte MCP server and CLI, enabling file operations, hybrid search, AI document Q&A, knowledge base queries, and collaboration tools.

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

egnyte As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install egnyte@claude-community

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

Only egnyte has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of egnyte 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: egnyte · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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