MCP Filesystem Server
Anthropic's reference MCP server for filesystem access. Read, write, search, move, and list files inside a configured allowlist of directories. The canonical example for understanding how MCP tool exposure works in practice — most third-party MCP servers borrow its argument-validation patterns.
Overview
Anthropic's reference MCP server for filesystem access. Read, write, search, move, and list files inside a configured allowlist of directories. The canonical example for understanding how MCP tool exposure works in practice — most third-party MCP servers borrow its argument-validation patterns.
Stack & relationships
How MCP Filesystem Server relates to other entries in the catalog — recommended pairings, alternatives, dependencies, and edges to avoid. Each edge carries a one-line operator note from our editorial team.
Recommended stack
- Commonly deployed withClaude Desktop
The reference deployment example for MCP. Configure filesystem allowlists in Claude Desktop's MCP config; the server starts on app launch.
- Commonly deployed withClaude Code
Same wiring as Claude Desktop. Most agent workflows that need local-file access pull this server in.
- Pairs withMCP Git Server
Together they give an agent full local-repo awareness — filesystem reads files, git reads metadata (status / diff / log / blame).
Works with
- Integrates withOpenHands
Filesystem MCP is non-optional for OpenHands — it's how the agent reads and writes project files. Allowlist limits blast radius.
Featured in these stacks
The L3 execution stacks that pick this tool as a recommended component, with the one-line note explaining the role it plays in each.
- Stack · L3·Workstation tier·Role: File access (the agent's hands on the codebase)Build a local coding-agent stack (May 2026)
The Anthropic reference filesystem MCP server with strict directory allowlisting. Required for OpenHands to read and write project files; allowlist limits blast radius when the agent goes off the rails.
- Stack · L3·Workstation tier·Role: MCP filesystem (file access with allowlisting)Build a memory-enabled local agent stack (May 2026)
Strict directory allowlist limits the agent's blast radius. Required for any agent that edits files; non-optional for a memory-enabled agent that may take destructive actions based on remembered context.
- Stack · L3·Workstation tier·Role: MCP filesystem (strict allowlist)Build a fully offline coding stack (May 2026)
Reference Anthropic filesystem MCP. Strict directory allowlisting limits the agent's blast radius — non-optional for offline deployments where the network can't catch a destructive mistake.
Pros
- Anthropic-maintained reference implementation
- Strict directory allowlisting prevents path-escape attacks
- Stdio + remote transport support
Cons
- No content-type heuristics — large binary files come through raw
- Requires per-directory configuration for each project
Compatibility
| Operating systems | macOS Linux Windows |
| GPU backends | n/a |
| License | Open source · free (OSS, MIT) |
Runtime health
Operator-grade signals on how actively MCP Filesystem Server is being maintained, how fresh its measurements are, and what failure classes operators have flagged. Every label below is anchored to a real date or count — we never infer maintainer activity we can't show.
Release cadence
Derived from the most recent editorial signal on this row.
6 days since last refresh · source: lastUpdated
Benchmark freshness
How recent the editorial measurements on this runtime are.
No editorial benchmarks for this runtime yet.
Community reproduction
Submissions that match an editorial measurement on similar hardware.
No community reproductions on file yet.
Get MCP Filesystem Server
Frequently asked
Is MCP Filesystem Server free?
What operating systems does MCP Filesystem Server support?
Does MCP Filesystem Server need a GPU?
Reviewed by RunLocalAI Editorial. See our editorial policy for how we evaluate tools.
Related — keep moving
Verify MCP Filesystem Server runs on your specific hardware before committing money.