Mcp Server Filesystem
Let your agent read and write project files through MCP while restricting access to explicit allowed directories.
Overview
io.github.bytedance/mcp-server-filesystem is a MCP server for the Build phase that provides directory-scoped filesystem access for coding agents.
What is this MCP server?
- Required allowed-directories comma-separated list gates every file operation
- npm package @agent-infra/mcp-server-filesystem with stdio transport
- SSE mode on http://127.0.0.1 with required port (default 8089)
- Mirrors common agent-infra pattern shared with commands and browser servers
- Prevents unrestricted whole-disk access when configured conservatively
- Server version 1.0.0
- Required config: allowed-directories
- Default SSE port 8089
Community signal: 36.3k GitHub stars.
What problem does it solve?
Without filesystem tools, agents depend on you to manually apply every file change they suggest across the repo.
Who is it for?
Solo builders who want scoped repo editing from the agent with a clear comma-separated directory allow list.
Skip if: Operators who need enterprise DLP, audit trails, or access across arbitrary machine paths without boundaries.
What do I get? / Deliverables
Once allowed-directories are set, the agent can perform MCP-backed file operations only inside those paths while you build the product.
- Directory-bounded file read and write tools for the agent
- Optional SSE endpoint for clients that cannot use stdio
- Safer default posture than unrestricted full-disk MCP filesystem servers
Recommended MCP Servers
Journey fit
Filesystem MCP belongs in Build agent-tooling because it is how agents manipulate the codebase during implementation. Allowed-directory scoping is an integration concern between the host agent and the OS, not a standalone frontend or docs task.
How it compares
Scoped MCP file bridge, not Git hosting integration or a documentation generator skill.
Common Questions / FAQ
Who is io.github.bytedance/mcp-server-filesystem for?
Indie developers using MCP-enabled agents who need controlled read and write access to specific project folders during implementation.
When should I use io.github.bytedance/mcp-server-filesystem?
Use it during Build when the agent should edit code and configs directly in allowed repo directories instead of proposing diffs only.
How do I add io.github.bytedance/mcp-server-filesystem to my agent?
Add @agent-infra/mcp-server-filesystem to MCP settings, set required allowed-directories to your repo paths, pick stdio or SSE with port, and reload the host.