Mcp Filesystem
Let agents read and write project files through MCP while keeping all operations inside a single WORKSPACE_ROOT boundary.
Overview
io.github.Digital-Defiance/mcp-filesystem is a MCP server for the Build phase that performs advanced filesystem tasks for agents within a required WORKSPACE_ROOT sandbox.
What is this MCP server?
- Advanced filesystem operations with strict workspace confinement
- Required WORKSPACE_ROOT env var locks all paths to one directory
- npm package @ai-capabilities-suite/mcp-filesystem v0.1.9
- stdio MCP server from Digital-Defiance ai-capabilities-suite
- Server version 0.1.9
- WORKSPACE_ROOT required environment variable
Community signal: 3 GitHub stars.
What problem does it solve?
Unbounded file access makes agent-assisted coding risky, so solo builders need filesystem tools that cannot wander outside the project directory.
Who is it for?
Builders standardizing a sandboxed file MCP next to Claude Code or Cursor for day-to-day repo work.
Skip if: Setups that require cross-machine file access, arbitrary system paths, or cloud object storage instead of local workspace files.
What do I get? / Deliverables
Agents gain reliable read/write filesystem capabilities limited to WORKSPACE_ROOT, improving safe automation during implementation.
- Bounded filesystem tool access for agents
- Configurable single-repo file automation surface
Recommended MCP Servers
Journey fit
Canonical shelf is Build because filesystem MCP is core agent tooling while you implement features and refactors in the repo. Agent-tooling subphase matches bounded file ops that power codegen, edits, and scaffolding—not end-user frontend polish alone.
How it compares
Sandboxed filesystem MCP integration, not a cloud storage connector or Git hosting API.
Common Questions / FAQ
Who is io.github.Digital-Defiance/mcp-filesystem for?
Solo developers who want agent file operations confined to one project directory via an explicit WORKSPACE_ROOT setting.
When should I use io.github.Digital-Defiance/mcp-filesystem?
Use it during Build agent-tooling setup and whenever multi-file edits must stay inside a single repo root for safety.
How do I add io.github.Digital-Defiance/mcp-filesystem to my agent?
Install @ai-capabilities-suite/mcp-filesystem, set WORKSPACE_ROOT to your repo absolute path in the MCP server env, then register the stdio server in your host config.