Summary
Built for the case where the official filesystem server gets slow.
The maintainers say plainly that the official Filesystem MCP Server already reaches WSL files through the \\wsl.localhost network path. This exists for large directory trees and search-heavy work, where running find and grep inside the distribution beats walking directories from Node. Both can run side by side.
What it is
A Node.js MCP server for filesystem operations inside Windows Subsystem for Linux, forked from the official Filesystem MCP Server and reimplemented around native Linux commands.
What you get
- Files read one at a time, several at once, or in numbered parts for files too large to take whole
- Files written, and edited with Git-style multi-line matching
- A dry-run option on edits, so a change can be previewed before it is applied
- Directories created, listed and deleted, files and directories moved, and file metadata read
- Search inside a distribution using WSL's own `find` and `grep`, which is where the speed difference over recursive Node traversal shows
- Multiple WSL distributions supported from the same Windows host
Requirements
Windows with WSL and at least one distribution installed, plus Node. Access is limited to the directories you list in `args` — nothing outside them is reachable.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary