Filesystem
Give your agent structured read, create, and edit access to project files through MCP instead of ad-hoc shell cat and echo.
Overview
Filesystem MCP is a MCP server for the Build phase that exposes read, create, and edit file operations to coding agents over stdio or local HTTP.
What is this MCP server?
- Read, create, and edit files via MCP tools (registry description)
- stdio via npx or streamable HTTP on localhost:3000 when MCP_TRANSPORT=http
- Version 1.3.0 on npm identifier filesystem-mcp
- Useful for local repos, generators, and multi-file edits from Claude Code or Cursor
- HTTP mode requires explicit MCP_TRANSPORT environment variable
- Server version 1.3.0
- Two transports: stdio and streamable-http (localhost:3000/mcp)
- npm package identifier filesystem-mcp
Community signal: 1 GitHub stars.
What problem does it solve?
Agents without a dedicated filesystem MCP either fumble multi-file edits or rely on opaque shell commands that are hard to audit and repeat.
Who is it for?
Builders running Claude Code, Cursor, or Codex who want a standard local filesystem bridge for day-to-day coding agents.
Skip if: Production remote file management across untrusted machines without additional sandboxing, or teams that forbid any agent write access to disk.
What do I get? / Deliverables
Your agent gets consistent file CRUD tools so implementation tasks finish faster with clearer, MCP-shaped actions you can log and constrain.
- MCP tools to read, create, and edit workspace files
- Optional HTTP MCP endpoint for clients that do not use stdio
Recommended MCP Servers
Journey fit
Filesystem MCP sits in Build because it is core agent tooling while you implement features, refactors, and docs in the repo. Agent-tooling is the right shelf for MCP servers that extend what the coding agent can touch on disk safely and consistently.
How it compares
Low-level MCP filesystem bridge, not a cloud IDE or git-centric code review skill.
Common Questions / FAQ
Who is Filesystem MCP for?
Solo developers and agent users who need reliable local file read/write tools inside MCP-compatible coding assistants.
When should I use Filesystem MCP?
Use it during active Build work whenever your agent must create modules, patch configs, or batch-edit repository files through MCP.
How do I add Filesystem MCP to my agent?
Add the npm package filesystem-mcp with stdio and npx, or run HTTP mode by setting MCP_TRANSPORT=http and pointing the client at http://localhost:3000/mcp.