Filesystem MCP Server

What it does

• Read/write access scoped to explicit allow-listed directories — the server refuses everything else
• Full toolset: read_file, read_multiple_files, write_file, edit_file, create_directory, list_directory, directory_tree, move, search_files, get_file_info
• directory_tree and recursive search for fast orientation in unfamiliar repos
• Runs locally over stdio via npx — no daemon, no network service, no accounts

When to use it

The default first MCP server for local-agent work: codebase exploration, bulk refactors, writing reports into a folder, or any task where Claude needs real files under your control. Pair with git-mcp so file changes stay versioned.

Getting started

Add to .mcp.json under mcpServers.filesystem:

{
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects", "/tmp/claude-scratch"]
}

Every argument after the package name is an allowed directory; only those paths are reachable.

Things to know

Safety equals your allow-list: mounting $HOME defeats the purpose, so scope to project directories plus a scratch dir if writes are needed. There is no undo inside the server — destructive writes are permanent, so keep everything under version control.