Filesystem MCP
Wire full local filesystem access into your agent so it can read, write, and organize project files within allowed roots during implementation.
Overview
Filesystem MCP is a MCP server for the Build phase that lets coding agents read and write files within configured local directory roots.
What is this MCP server?
- Full filesystem interaction for LLMs via MCP stdio (@j0hanz/filesystem-mcp v1.9.1)
- Optional positional root directory arguments to cap accessible paths
- Supports MCP Roots protocol or --allow-cwd for flexible sandboxing
- Standard choice for Claude Code-style implementations that create and edit files
- Pairs with read-only filesystem-context MCP when you split browse vs write sessions
- Version 1.9.1, package @j0hanz/filesystem-mcp on npm
- stdio transport; optional repeated filepath root arguments
- Repository: github.com/j0hanz/filesystem-mcp
Community signal: 8 GitHub stars.
What problem does it solve?
Without filesystem MCP, agents cannot reliably create or update project files on your machine during an implementation session.
Who is it for?
Solo builders running Claude Code or Cursor with agentic editing who need first-class local file operations via MCP.
Skip if: Cloud-only sandboxes where the agent never touches a local checkout, or teams that forbid any MCP write access.
What do I get? / Deliverables
After you scope roots and register the server, agents can perform multi-file edits and scaffolding inside allowed directories.
- Agent-driven file create, read, update, and organize operations within scoped roots
- Repeatable local dev workflow without manual copy-paste from chat
- Configurable path boundaries via arguments or MCP Roots protocol
Recommended MCP Servers
Journey fit
Mutable filesystem tools are core Build infrastructure for agent-driven coding, scaffolding, and refactors. Agent-tooling is the shelf where MCP filesystem servers belong in a solo builder’s default stack next to git and terminal tools.
How it compares
Writable local filesystem MCP, not read-only filesystem-context or a remote GitHub-contents API integration.
Common Questions / FAQ
Who is filesystem-mcp for?
Indie developers and small teams using MCP-enabled agents who want direct, root-scoped read and write access to a local project tree.
When should I use filesystem-mcp?
Use it during active Build work when the agent must create files, apply patches, or reorganize directories under paths you trust.
How do I add filesystem-mcp to my agent?
Install @j0hanz/filesystem-mcp, add a stdio MCP entry, and pass allowed directory paths as package arguments or via MCP Roots in your client config.