Ext Ops Panel
Open dashboard
Comparison

ellmos FileCommander vs Linux Filesystem

ellmos FileCommander is an MCP server published by ellmos-ai. Marketplaces we read that list it: 1 (Official MCP Registry). Linux Filesystem is an MCP server published by rghsoftware. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceellmos FileCommanderLinux Filesystem
Official MCP Registry Listed
Version: 1.9.3
Downloads/month (npm): 679
Downloads/week (npm): 69
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 1.2.1
No figure published
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

ellmos FileCommander vs Linux Filesystem
Factellmos FileCommanderLinux Filesystem
Marketplaces that list it11
Stars (GitHub) (differs)5No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ellmos-filecommander-mcp)On your machine (https://github.com/rghsoftware/linux-filesystem-extension/releases/download/v1.2.1/linux-filesystem.mcpb)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/ellmos-ai/ellmos-filecommander-mcpNot stated
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

ellmos FileCommander

In its own words, on Official MCP Registry:

Filesystem MCP server: files, processes, sessions, async search, OCR, archives, safe delete.

Linux Filesystem

In its own words, on Official MCP Registry:

Enhanced Linux filesystem access with symlinks, permissions, and chmod support

How to run each

ellmos FileCommander As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ellmos-filecommander-mcp -- npx -y ellmos-filecommander-mcp

Linux Filesystem

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

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

What it can do: ellmos FileCommander · What it can do: Linux Filesystem · Compare two other plugins

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