Bulk Filesystem Operations MCP Server

What is Bulk Filesystem Operations MCP Server?

A FastMCP server that exposes tools for performing bulk file and folder operations, including centralized exception handling. It is designed for users who need to execute multiple filesystem actions efficiently via an MCP client.

How to use Bulk Filesystem Operations MCP Server?

Install and run via uvx with the repository URL. Configure the server in your MCP client (e.g., VS Code, Roo Code/Cline) by adding the appropriate JSON block with server name, command, and arguments. The server provides tools under file and folder namespaces, along with call_tool_bulk and call_tools_bulk for batch requests.

Key features of Bulk Filesystem Operations MCP Server

• Perform batch calls to a single tool using call_tool_bulk.
• Execute multiple different tools in one request via call_tools_bulk.
• Read, create, append, erase, move, and delete files.
• Create, list, read all, move, delete, and empty folders.
• Disable specific file or folder tools using environment variables.
• Recursive folder operations are available but can be expensive.

Use cases of Bulk Filesystem Operations MCP Server

• Batch reading the contents of multiple files in one call.
• Bulk creating or deleting many files/folders without multiple round-trips.
• Moving or copying entire folder structures efficiently.
• Erasing file contents across many files at once.

FAQ from Bulk Filesystem Operations MCP Server

What runtime is required to run Bulk Filesystem Operations MCP Server?

The server requires uvx to execute. It is a Python-based FastMCP server.

How can I disable specific tools?

Set the DISABLE_FILE_TOOLS or DISABLE_FOLDER_TOOLS environment variable to an array of tool names. For example, DISABLE_FILE_TOOLS=["file_read"].

Are there any limitations on bulk operations?

Bulk tools (call_tool_bulk, call_tools_bulk) cannot currently be disabled. Also, the folder_read_all tool can be expensive, especially when used recursively.

Where does the server access files?

The server operates on the local filesystem of the machine where it runs. No external storage or cloud integration is mentioned.

What transport and authentication does the server support?

The README shows an SSE endpoint in the VS Code debug configuration. No authentication mechanism is described.