MCP -Filesystem

MCP -Filesystem is an enhanced MCP server that exposes a suite of filesystem operations via MCP client tooling. It provides robust read and write capabilities, directory management, and a secure, feature-rich interface for working with files and directories through MCP requests. Core tools include read_file, read_multiple_files, write_file, delete_file, edit_file, search_files, list_directory, create_directory, get_file_info, move_file, run_command, and list_allowed_directories. These tools are designed to fix common limitations found in standard MCP filesystem implementations such as improved glob pattern handling, combined head/tail reads, and diff-preview-enabled editing. The server is intended to be consumed by MCP clients (e.g., VS Code MCP integrations, Cursor IDE, Windsurf AI Editor) to perform filesystem operations across a controlled workspace.

Prerequisites:

• Node.js v18 or newer
• npm (bundled with Node.js) or pnpm/yarn if preferred

Installation options:

Option 1: Install globally via NPM (recommended for quick start)

npm install -g @redf0x1/mcp-server-filesystem

Usage (global):

mcp-server-filesystem /path/to/allowed/directory

Option 2: Install locally (per project)

git clone https://github.com/redf0x1/mcp-server-filesystem.git
cd mcp-server-filesystem
npm install

Usage (local):

node server-filesystem.js /path/to/allowed/directory

Option 3: Run with NPX (no installation required)

npx @redf0x1/mcp-server-filesystem /path/to/allowed/directory

Prerequisites recap: Ensure your environment meets Node.js v18+, and you have an accessible workspace path that you authorize for server operation.

Notes and tips:

• The server accepts multiple allowed directories when launched via NPX or local node invocation; specify each path as separate arguments where supported by the client configuration.
• In MCP client configs, the cwd field may be used when running from a local installation to point to the server directory.
• For secure environments, consider using environment variables like NODE_ENV to control behavior (e.g., development vs. production).
• If you encounter issues with glob patterns, verify the read/write permissions of the target directories and ensure the paths are correctly mounted in containerized setups.
• When using Docker integration, bind mounts should reflect your host workspace and data directories correctly to avoid permission or path resolution problems.