ellmos FileCommander vs io.github.fieldcure/filesystem
ellmos FileCommander is an MCP server published by ellmos-ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.fieldcure/filesystem is an MCP server published by fieldcure. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  ellmos FileCommander |  io.github.fieldcure/filesystem |
|---|---|---|
| Official MCP Registry | Listed Version: 1.11.4 Downloads/month (npm): 434 Downloads/week (npm): 151 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 1.1.2 Forks (GitHub): 1 Stars (GitHub): 1 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
| Fact | ellmos FileCommander | io.github.fieldcure/filesystem |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | 2026-10-25 | Not published |
| Where it runs (differs) | On your machine (ellmos-filecommander-mcp) | On your machine (FieldCure.Mcp.Filesystem) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ellmos-ai/ellmos-filecommander-mcp | github.com/fieldcure/fieldcure-mcp-filesystem |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Filesystem MCP server: files, previews, search, processes, OCR, archives, safe delete, web fetch.
io.github.fieldcure/filesystem
Secure MCP server for sandboxed filesystem operations with document parsing support.
How to run each
ellmos FileCommander As a local MCP server: npm package
claude mcp add --transport stdio ellmos-filecommander-mcp -- npx -y ellmos-filecommander-mcpio.github.fieldcure/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: io.github.fieldcure/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.