io.github.Digital-Defiance/mcp-filesystem vs Filesystem MCP
io.github.Digital-Defiance/mcp-filesystem is an MCP server published by Digital-Defiance. Marketplaces we read that list it: 1 (Official MCP Registry). Filesystem MCP is an MCP server published by j0hanz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  io.github.Digital-Defiance/mcp-filesystem |  Filesystem MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.9 Downloads/month (npm): 181 Downloads/week (npm): 37 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 2.11.0 Downloads/month (npm): 5 072 Downloads/week (npm): 1 391 Forks (GitHub): 7 Stars (GitHub): 26 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 | io.github.Digital-Defiance/mcp-filesystem | Filesystem MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (worse) | 26 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 7 (better) |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | On your machine (@ai-capabilities-suite/mcp-filesystem) | On your machine (@j0hanz/filesystem-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 0 | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/digital-defiance/ai-capabilities-suite | github.com/j0hanz/filesystem-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| 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
io.github.Digital-Defiance/mcp-filesystem
Advanced filesystem operations with strict security boundaries for AI agents
Filesystem MCP
Filesystem MCP server for AI assistants.
How to run each
io.github.Digital-Defiance/mcp-filesystem As a local MCP server: npm package
claude mcp add --env "WORKSPACE_ROOT=<YOUR_WORKSPACE_ROOT>" --transport stdio mcp-filesystem -- npx -y @ai-capabilities-suite/mcp-filesystemRequires: WORKSPACE_ROOT
Filesystem MCP As a local MCP server: npm package
claude mcp add --transport stdio filesystem-mcp -- npx -y @j0hanz/filesystem-mcpCommands 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 io.github.Digital-Defiance/mcp-filesystem asks for
WORKSPACE_ROOT
Only Filesystem MCP asks for
FS_ALLOWED_DIRS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.Digital-Defiance/mcp-filesystem · What it can do: Filesystem MCP · 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.