Filesystem MCP Server

@gomcpgo

代码仓库

基本信息

分类

文件与存储

传输方式

stdio

作者

gomcpgo

关于 Filesystem MCP Server

Enhanced FileSystem MCP server

Filesystem MCP Server 配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块，请前往代码仓库查看安装说明。

代码仓库

Filesystem MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Filesystem MCP Server?

A secure, single-binary MCP server for filesystem operations with no runtime dependencies. It provides 18 tools for reading, writing, searching, and managing files within sandboxed directories, and is designed for AI coding workflows with Claude Desktop and Claude Code.

How to use Filesystem MCP Server?

Download the binary for your platform from the Releases page, make it executable, and set the MCP_ALLOWED_DIRS environment variable to a comma-separated list of allowed absolute paths. Then connect to any MCP client by specifying the binary as the command and the environment variable in the client’s configuration (e.g., claude_desktop_config.json for Claude Desktop).

Key features of Filesystem MCP Server

18 tools covering read, write, search, replace, insert, and file management
Dry-run preview for replacement and insertion tools
Secure by default with path validation and symlink attack prevention
Single binary, no Node.js, Python, or other runtime required
Tested with Claude Desktop and Claude Code for real-world coding workflows
Detailed error messages explaining why access was blocked

Use cases of Filesystem MCP Server

Read, edit, and refactor files in AI-assisted coding sessions
Batch replace text or apply regex patterns across multiple files
Search codebase with recursive regex, respecting file type filters
Preview file changes before applying them via dry-run mode
Manage directories and files (create, move, list, get metadata) within a sandboxed scope

常见问题

What runtime does Filesystem MCP Server require?

No runtime dependencies – it is a single, pre-compiled binary for macOS, Linux, or Windows.

How do I restrict which directories the server can access?

Set the `MCP_ALLOWED_DIRS` environment variable with a comma-separated list of absolute paths. The server will only operate within those directories.

Can I preview changes before applying them?

Yes, all replacement and insertion tools support a `dry_run` parameter that shows what would be changed without modifying any files.

How does the server prevent unauthorized file access?

It resolves all paths to their canonical form, blocks `../` traversal attempts, validates that symlink targets stay inside allowed directories, and rejects broken symlinks. Access denials are logged with a `SECURITY:` prefix.