Loading...
This MCP server provides access to the local filesystem, enabling read, write, and management operations within specified allowed directories.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server provides access to the local filesystem, enabling read, write, and management operations within specified allowed directories.
This server is relatively safe when configured with carefully chosen allowed directories and used for read-only operations. However, the write and delete capabilities pose a significant risk if the allowed directories are too broad or if the server is used by untrusted actors.
Performance will be limited by disk I/O speed. Large file operations may take significant time. Consider the impact of recursive directory searches on performance.
The primary cost is the computational resources used to run the server. Disk I/O can also be a factor in terms of resource utilization.
{
"mcpServers": {
"filesystem": {
"command": "mcp-filesystem-server",
"args": ["/path/to/allowed/directory", "/another/allowed/directory"]
}
}
}read_fileReads the complete contents of a specified file.
Read-only operation, no side effects.
read_multiple_filesReads the contents of multiple files in a single operation.
Read-only operation, no side effects.
write_fileCreates a new file or overwrites an existing file with specified content.
Can overwrite or create files, potentially leading to data loss or corruption.
copy_fileCopies files and directories from a source to a destination.
Can create copies of sensitive files in unintended locations.
move_fileMoves or renames files and directories.
Can move files to unintended locations, potentially disrupting workflows or hiding data.
delete_fileDeletes a file or directory from the file system.
Can permanently delete files and directories, leading to data loss.
modify_fileUpdates a file by finding and replacing text using string matching or regex.
Can modify file contents, potentially introducing errors or malicious code.
list_directoryGets a detailed listing of all files and directories in a specified path.
Read-only operation, no side effects.
create_directoryCreates a new directory or ensures a directory exists.
Can create new directories, potentially altering the file system structure.
treeReturns a hierarchical JSON representation of a directory structure.
Read-only operation, no side effects.
search_filesRecursively searches for files and directories matching a pattern.
Read-only operation, no side effects.
search_within_filesSearches for text within file contents across directory trees.
Read-only operation, no side effects.
get_file_infoRetrieves detailed metadata about a file or directory.
Read-only operation, no side effects.
list_allowed_directoriesReturns the list of directories that this server is allowed to access.
Read-only operation, no side effects.
None
This server is relatively safe when configured with carefully chosen allowed directories and used for read-only operations. However, the write and delete capabilities pose a significant risk if the allowed directories are too broad or if the server is used by untrusted actors.
Autonomy is highly dependent on the configured allowed directories. Without careful configuration, destructive tools can cause significant damage.
Production Tip
Carefully restrict the allowed directories to the minimum necessary set to reduce the risk of accidental or malicious file operations.
Configure the allowed directories when starting the server. Only files and directories within these allowed paths will be accessible.
The server will return an error indicating that the file is not accessible.
No, this server does not have built-in authentication. Access control is based solely on the allowed directories.
It depends on the allowed directories configuration. If the allowed directories include system files, then yes. However, this is generally not recommended due to the risk of system instability.
Carefully configure the allowed directories and limit write access to trusted users or processes. Consider implementing backups.
No, it is generally not safe to expose this server directly to the internet without additional security measures such as a firewall and intrusion detection system.
The documentation mentions size limits for inline content and base64 encoding, but specific values are not provided. You may need to test to determine the exact limits.