Build Your Own FileSystem MCP Server - n8n Workflow | Neura Market
Build Your Own FileSystem MCP Server
**This template is for self-hosted n8n instances only.**
### This n8n demonstrates how to build a simple FileSystem MCP server. Connecting to this server allows MCP clients and agents to list, read, and create directories and files on the local machine or remote server.
This MCP example is based off an official MCP reference implementation which can be found here - [https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem](https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem)
### How it works
- A MCP server trigger is used and connected to 5 tools: 3 Execute Command tools and 2 custom workflow tools.
- The 3 Execute Command tools allow for listing, searching, and creating directories.
- The 2 custom workflow tools are for reading and writing files to disk.
- Special care has been taken to not allow the MCP agent to execute arbitrary Linux commands on the target server. This is achieved by only allowing the agent to provide parameters such as filenames and paths rather than raw commands.
### How to use
- This Filesystem MCP server will write to the server which hosts the n8n instance - this can be your local machine or a remote server. If your target filesystem is on neither, then modify the commands to connect to the desired server.
- Connect your MCP client by following the n8n guidelines here - https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/#integrating-with-claude-desktop
- Try the following queries in your MCP client:
- Please help me list all folders under the project directory.
- Help me create a bash script to send a notification to Slack.
- Search for the log file on the 22nd April and read its contents. What was the cause of the outage?
### Requirements
- Linux file system for this example template. Feel free to modify if working on Windows.
- MCP Client or Agent for usage such as Claude Desktop - https://claude.ai/download
### Customizing this workflow
- Implement the moving and renaming of files by adding more custom workflow tools to the MCP server.
- Remember to set the MCP server to require credentials before going to production and sharing this MCP server with others!
Platform
n8n
Category
File & Document Management
Price
Free
Creator
Jimleuk
integrating-with-claude-desktop
switch
stickyNote
executeCommand
executeCommandTool
mcpTrigger
toolWorkflow
executeWorkflowTrigger
How to import this workflow into n8n
1Purchase or download the workflow to get the n8n workflow JSON file.
2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
3Open each node marked with a credential warning and connect your own accounts and API keys.
4Run the workflow once manually to verify the data flow, then toggle it to Active.