bash_execute
Execute a Bash command directly with output capture. More flexible than execute_command but still with security restrictions. Allows for direct access to Bash functionality.
LABSCO SUMMARY
Reading files, editing them and running commands against them all come from one server.
list_allowed_directories is the call to make first, because every file operation is confined to what it returns. Editing is line-based and hands back a git-style diff, with a dry run available, which makes a change reviewable before it is written. The execution side is wider than the file side — a checked command runner, direct bash with environment and timeout, piped sequences, and curl with method, headers and data — and the vendor describes those as carrying security restrictions rather than the same directory confinement.
What it is
A filesystem server scoped to allowed directories, with command execution and an HTTP request tool alongside it.
What you get
- Files read one at a time or several at once with an encoding, written whole, and edited by exact line sequences returning a git-style diff, with a dry run available.
- Directories created including nested paths, listed with file and directory markers, and returned as a recursive JSON tree.
- Files and directories moved or renamed in one operation, failing rather than overwriting when the destination already exists.
- Recursive case-insensitive search by partial name with exclude patterns, and file metadata covering size, creation and modification times, permissions and type.
- The list of directories the server may touch, and performance metrics for its own operations.
- Command execution: a checked command runner, direct bash with environment variables and a timeout, piped bash sequences returning both stdout and stderr, and curl requests with method, headers and body.
Requirements
Directories explicitly allowed on the server, since every file operation is confined to them, plus bash and curl on the host for the execution tools.
Setup effort
One command — npx -y @gabrielmaialva33/mcp-filesystem <YOUR_PATH_TO_ALLOWED_DIRECTORY>
USE CASES
01
Making a change to a file you can review before it lands
Line-based edits return a git-style diff, and the dry run shows that diff without writing anything.
02
Getting your bearings in a directory you have not seen
What the server may touch comes first, then the shape of the tree, then one level in detail.
03
Finding the files that mention what you are chasing
Search finds candidates by name, reading several at once compares them, and the metadata says which are worth opening at all.
04
Running a build from the same place you read the source
Commands run with an environment and a timeout, and a piped sequence returns both streams, which is where build failures usually live.
05
Calling an HTTP API without leaving the session
Method, headers and body are all parameters, so a request to an external service is one call rather than a script.
16 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
bash_pipe
Execute a sequence of Bash commands piped together. Allows for powerful command combinations with pipes. Results include both stdout and stderr.
create_directory
Create a new directory or ensure a directory exists. Can create multiple nested directories in one operation. If the directory already exists, this operation will succeed silently. Perfect for setting up directory structures for projects or ensuring required paths exist. Only works within allowed directories.
curl_request
Execute a curl request to an external HTTP API. Allows specifying URL, method, headers, and data. Useful for integrating with external services via HTTP.
directory_tree
Get a recursive tree view of files and directories as a JSON structure. Each entry includes 'name', 'type' (file/directory), and 'children' for directories. Files have no children array, while directories always have a children array (which may be empty). The output is formatted with 2-space indentation for readability. Only works within allowed directories.
edit_file
Make line-based edits to a text file. Each edit replaces exact line sequences with new content. Returns a git-style diff showing the changes made. Only works within allowed directories.
execute_command
Execute a system command with security restrictions. Validates commands for safety and provides detailed output. Limited to basic system operations with security checks.
get_file_info
Retrieve detailed metadata about a file or directory. Returns comprehensive information including size, creation time, last modified time, permissions, and type. This tool is perfect for understanding file characteristics without reading the actual content. Only works within allowed directories.
get_metrics
Returns performance metrics about server operations. Useful for monitoring and debugging.
list_allowed_directories
Returns the list of directories that this server is allowed to access. Use this to understand which directories are available before trying to access files.
list_directory
Get a detailed listing of all files and directories in a specified path. Results clearly distinguish between files and directories with [FILE] and [DIR] prefixes. This tool is essential for understanding directory structure and finding specific files within a directory. Only works within allowed directories.
move_file
Move or rename files and directories. Can move files between directories and rename them in a single operation. If the destination exists, the operation will fail. Works across different directories and can be used for simple renaming within the same directory. Both source and destination must be within allowed directories.
read_file
Read the complete contents of a file from the file system. Handles various text encodings and provides detailed error messages if the file cannot be read. Use this tool when you need to examine the contents of a single file. Only works within allowed directories.
read_multiple_files
Read the contents of multiple files simultaneously. This is more efficient than reading files one by one when you need to analyze or compare multiple files. Each file's content is returned with its path as a reference. Failed reads for individual files won't stop the entire operation. Only works within allowed directories.
search_files
Recursively search for files and directories matching a pattern. Searches through all subdirectories from the starting path. The search is case-insensitive and matches partial names. Returns full paths to all matching items. Great for finding files when you don't know their exact location. Only searches within allowed directories.
write_file
Create a new file or completely overwrite an existing file with new content. Use with caution as it will overwrite existing files without warning. Handles text content with proper encoding. Only works within allowed directories.
BEFORE YOU INSTALL
What to know first
Tools you get
16 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 16 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-filesystem": {
"command": "npx",
"args": [
"-y",
"@gabrielmaialva33/mcp-filesystem",
"<YOUR_PATH_TO_ALLOWED_DIRECTORY>"
]
}
}
}<YOUR_PATH_TO_ALLOWED_DIRECTORY> is the directory the server may work in. List more directories as further arguments. Every file operation is confined to them.
npx
TERMINAL
npx -y @gabrielmaialva33/mcp-filesystem <YOUR_PATH_TO_ALLOWED_DIRECTORY>
