Name: Filesystem
Author: j0hanz

Filesystem MCP

Filesystem MCP server for AI assistants.

Grade A Local · stdio No auth needed tools not listed v2.19.2 · 7 Nov 2026 MIT

No reviews yet by j0hanznpm 25,811 Runs on your machine, nothing hosted

97/100

trust score

936

downloads a day

local

runs on your machine

downloads in 30d

What it does

Filesystem MCP server for AI assistants.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user j0hanz-filesystem-mcp '--' npx -y @j0hanz/filesystem-mcp

Filesystem costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

j0hanz11 servers

6 categories

All 11 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Filesystem as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user j0hanz-filesystem-mcp '--' npx -y @j0hanz/filesystem-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take FS_ALLOWED_DIRS (Allowed directories; ':'-separated on Unix, ';'-separated on Windows. Alternative to positional arguments.), FS_READ_ONLY_DIRS (Read-only directories; ':'-separated on Unix, ';'-separated on Windows. Writes, moves, and deletes under them are refused.) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

This listing has not published its tool surface here yet, so what a client will ask you to approve is whatever the manifest declares at install time.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Filesystem or to call it, at any volume.

ATrust score 97 / 100

Release 2.19.2 · scanned 7 Nov 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score97

Findings3 threat · 0 capability

Capabilitymoderate

Coveragesource

Verificationsource

Surface digesteac2c23a5427af752663e6f63ab2f07badf08476700283a99a5d7943858fec46

Score vectorthreat 100 → client 97

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	source	publisher verification (provenance) — cryptographic build provenance ties the artifact to its source	−0
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfacenot available

Implementation sourceread

Package metadataread

Live transportnot available

No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
No per-tool rows for this release — see the note below.

reads sensitive or local data

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digesteac2c23a5427af75

Scanned2026-11-07

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Release history

Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 2.19.2. Pin a release below and the command asks for exactly that one.

2.19.2

7 Nov 2026

latest