Lets AI manage files, search content, archive data, hash, and detect duplicates.
This MCP tool claims broad local file system operations, requires no secrets, and declares no remote endpoints; its main exposure is the inherent local execution and file read/write capability typical of such tools. It is open-source and partially auditable, but the third-party registry origin, missing README, no declared license, and weak adoption/maintenance signals warrant a cautionary overall posture.
The material explicitly states that no keys or environment variables are required, and no API tokens, account credentials, or other sensitive authentication inputs are requested, so credential exposure and abuse risk appears low.
The material declares no remote endpoints, and the description only mentions filesystem operations; there is no factual indication that user data is sent to external services. Based on the provided material, network egress risk appears low.
The system checks indicate it executes code, and as an MCP tool it has the ability to perform local file management, archiving, hashing, and duplicate detection, implying local process execution and system-call access. This is a normal capability for this class of tool, but its runtime boundary and host permissions should be controlled.
The description states support for filesystem CRUD, search, archive, hashing, and duplicate detection, which implies the ability to read, modify, delete, and traverse local file data within whatever directories are exposed to it. The material does not specify granular path restrictions or sandboxing, so its effective file scope should be constrained.
A positive factor is that an open-source repository exists, enabling code review; however, it comes from a third-party registry, lacks a README, has no declared license, shows 0 stars, and has unknown maintenance status, which are weak trust and upkeep signals. There is no concrete red flag strong enough to rate it as high risk, but the source and dependencies should be reviewed before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "File Manager MCP" yet — see the docs or source repo.
Scan the /project directory, move log files into a logs subfolder, archive temp files not modified in 30 days into archive.zip, and return a processing summary.
A list of moved and archived files, plus the archive path and an execution summary.
Run duplicate file detection on /data/assets, list duplicates by hash, group removable copies together, but do not delete anything.
Grouped duplicate files with hashes, file paths, and suggested originals to keep.
Search the /shared directory for files containing the keyword "password" or ".env", list their paths and modified times, and create a review summary.
A list of matching files, modification times, and a concise summary for security review.
Safely let AI read, write, move, copy, and manage files.
Search files, inspect directories, and read text, PDF, and DOCX content.
Securely lets AI browse, search, and understand local project files.
Safely read, write, search, and manage files in a sandboxed environment.
Manage files and folders with natural language, batch actions, and advanced editing.
Restrict AI file access to one folder with safe read-only defaults.