J
j0hanz/filesystem-mcp
Search, read and edit files in directories you choose
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Client config (built from the install command this repo gives)
{
"mcpServers": {
"j0hanz-filesystem-mcp": {
"command": "npx",
"args": ["-y", "@j0hanz/filesystem-mcp@latest", "/path/to/project"]
}
}
}Parsed from the README we fetched on 2026-11-06; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"j0hanz-filesystem-mcp": {
"command": "npx",
"args": ["-y", "@j0hanz/filesystem-mcp@latest", "/path/to/project"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio j0hanz-filesystem-mcp -- npx -y @j0hanz/filesystem-mcp@latest /path/to/project
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
npx -y @j0hanz/filesystem-mcp@latest /path/to/project
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y @j0hanz/filesystem-mcp@latest /path/to/project. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# Filesystem MCP
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
Let your AI assistant work with your files, safely.
Read, search, edit, and patch files in the folders you choose.
Secret files stay hidden, and risky changes wait for your OK.
Real sessions with a real model, except the web client demo. The apply? prompt comes from the example gatekeeper client, not the server.
Undo skips a file you edited since, so your edit stays
Rename across a repo, reviewed as one diff, with dist/ and .env untouched
Bring back a deleted folder that git can't restore
Secret files stay hidden, and overwrites wait for your OK
Move files into an archive, then undo a move that overwrote one
Review different edits to three files as one diff before they are written
A patch that no longer fits changes nothing
Find a crash in a 14 MB log without reading all of it
## What is this?
Model Context Protocol (MCP) is how AI apps
such as Claude, GitHub Copilot in VS Code, and Cursor connect to tools.
Filesystem MCP is an MCP server: a small program that runs on your computer
and gives the AI 14 tools for working with files. You choose which folders it
can use, and everything outside them is off limits.
Once it is connected, you can ask things like:
"Find every TODO in this repo and group them by file."
"Rename getUser to fetchUser in all .ts files. Show me the diff first."
"What changed between config.dev.json and config.prod.json?"
"Read the last 50 lines of server.log and explain the error."
"Move the old screenshots into archive/2025/."
## Why Filesystem MCP?
It is safe by default. The AI can use only the folders you allow, and
.env files, private keys, and cloud credentials are blocked. The server
asks you before the AI deletes a non-empty folder, opens a folder you did
not allow, or writes over a file with create or move. These questions
need a client that can show them. If yours cannot, the server refuses each
of those actions instead of asking. Only create and copies can skip the
question, because overwrite: true replaces a file without asking, on any
client. undo can usually restore a file create replaced, but a copy cannot
be undone. Edits made with edit, patch, and
replacetext apply without asking, but the AI can show you the diff first
with dryRun. If the AI should never change
anything, --read-only removes every tool that writes.
Search and editing are made for code. The AI can search inside files like
grep, with a regex engine (RE2) that cannot hang, and by default the
server skips .gitignored files and folders like nodemodules. Edits are
exact-match replacements that return an error when the text does not match,
and you can preview them as a diff first.
It saves the AI's context. The AI can read many files in one call or
only the lines it needs, and it can check a file's size and token estimate
before reading it.
It works with any MCP client, over stdio or HTTP, on macOS, Linux, and
Windows. You can install it with npx, Docker, or a one-click Claude Desktop
extension, or build your own client on it.
It is private. It runs on your machine, has no telemetry, and makes no
network calls.
### Compared with the reference server
How this server differs from the official
@modelcontextprotocol/server-filesystem,
Read, search, edit, and patch files in the folders you choose.
Secret files stay hidden, and risky changes wait for your OK.
Real sessions with a real model, except the web client demo. The apply? prompt comes from the example gatekeeper client, not the server.
Undo skips a file you edited since, so your edit stays
Rename across a repo, reviewed as one diff, with dist/ and .env untouched
Bring back a deleted folder that git can't restore
Secret files stay hidden, and overwrites wait for your OK
Move files into an archive, then undo a move that overwrote one
Review different edits to three files as one diff before they are written
A patch that no longer fits changes nothing
Find a crash in a 14 MB log without reading all of it
## What is this?
Model Context Protocol (MCP) is how AI apps
such as Claude, GitHub Copilot in VS Code, and Cursor connect to tools.
Filesystem MCP is an MCP server: a small program that runs on your computer
and gives the AI 14 tools for working with files. You choose which folders it
can use, and everything outside them is off limits.
Once it is connected, you can ask things like:
"Find every TODO in this repo and group them by file."
"Rename getUser to fetchUser in all .ts files. Show me the diff first."
"What changed between config.dev.json and config.prod.json?"
"Read the last 50 lines of server.log and explain the error."
"Move the old screenshots into archive/2025/."
## Why Filesystem MCP?
It is safe by default. The AI can use only the folders you allow, and
.env files, private keys, and cloud credentials are blocked. The server
asks you before the AI deletes a non-empty folder, opens a folder you did
not allow, or writes over a file with create or move. These questions
need a client that can show them. If yours cannot, the server refuses each
of those actions instead of asking. Only create and copies can skip the
question, because overwrite: true replaces a file without asking, on any
client. undo can usually restore a file create replaced, but a copy cannot
be undone. Edits made with edit, patch, and
replacetext apply without asking, but the AI can show you the diff first
with dryRun. If the AI should never change
anything, --read-only removes every tool that writes.
Search and editing are made for code. The AI can search inside files like
grep, with a regex engine (RE2) that cannot hang, and by default the
server skips .gitignored files and folders like nodemodules. Edits are
exact-match replacements that return an error when the text does not match,
and you can preview them as a diff first.
It saves the AI's context. The AI can read many files in one call or
only the lines it needs, and it can check a file's size and token estimate
before reading it.
It works with any MCP client, over stdio or HTTP, on macOS, Linux, and
Windows. You can install it with npx, Docker, or a one-click Claude Desktop
extension, or build your own client on it.
It is private. It runs on your machine, has no telemetry, and makes no
network calls.
### Compared with the reference server
How this server differs from the official
@modelcontextprotocol/server-filesystem,
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/j0hanz-filesystem-mcp/)
- Source
- awesome · https://github.com/j0hanz/filesystem-mcp
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.