A
licenseB
qualityC
maintenanceEnables AI assistants to list directories, read, write, and search files within a locked root directory, using resolve-then-validate path checks, size caps, and binary detection to prevent sandbox escapes.
4
MIT
bounded-filesystem-mcp
by shivam-bit
Related Servers
Alternatives to bounded-filesystem-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables secure filesystem operations with directory sandboxing and optional read-only mode. Supports file reading/writing, directory management, file searching, and text operations while restricting access to specified directories.12-
- AlicenseNot gradedqualityCmaintenanceEnables agents to read, write, edit, search, rename, move, and delete files, perform regex search-and-replace across trees, query and modify JSON documents, and inspect git status and diffs, all through structured tools instead of shell commands. Includes safeguards like dry-run previews, atomic multi-file edits, and protection for denied or sensitive paths.MIT
- AlicenseCqualityBmaintenanceEnables AI agents to list, read, inspect, write, and precisely edit files and to regex-search a workspace, with every path confined to a sandboxed root directory. Token-saving output such as line-range reads and match locations without line content keeps context use low while guarded writes and ambiguous edits prevent accidental data loss.6MIT
- AlicenseNot gradedqualityDmaintenanceProvides secure filesystem access for AI assistants with optimizations like file reading limits and depth-limited traversal to improve token efficiency. It enables AI models to read, write, and search files within explicitly allowed directories while automatically skipping large system folders.4MIT
- FlicenseNot gradedqualityDmaintenanceProvides sandboxed access to local filesystem operations including directory and file management, content search with glob and regex patterns, and binary file support with configurable safety limits.-
TDQS
A3.6/5.0
Scored across 14 tools
Disambiguation3/5
Most tools target clearly distinct operations, but read_file is an explicitly deprecated near-duplicate of read_text_file, and list_directory vs list_directory_with_sizes differ only by an extra field, which invites misselection. The descriptions do help (flagging deprecation and size detail), keeping it from being worse than middling.
Naming Consistency4/5
Strong snake_case verb_noun pattern throughout (read_file, write_file, create_directory, search_files, move_file). The only deviations are directory_tree, which is a bare noun with no verb, and the modifier suffixes on the read_*/list_* variants, which are still readable and predictable.
Tool Count4/5
14 tools is a reasonable, well-scoped surface for a bounded filesystem server and nearly every tool earns its place. Minor bloat comes from a deprecated read_file alias and a listing variant that could be a parameter rather than its own tool.
Completeness3/5
The surface covers read, write, edit, move, search, and inspection well, but there is no delete/remove operation at all, and no copy tool. Agents attempting cleanup or duplication workflows will hit dead ends and have to fall back to overwriting or external means.