MCP server for file system operations and shell execution within allowed directories in a dev container environment
Server provides 13 tools with consistent naming (verb_noun pattern) and descriptions. Most tools have input schemas defined via Zod. However, critical gaps exist: shell_exec lacks visible input schema; several tools have generic descriptions under 100 chars; no output schemas documented; error handling is minimal; no tool annotations (readOnlyHint/destructiveHint); parameter descriptions are sparse. Naming is strong (get_mode, set_mode, read_multiple_files, write_file, edit_file, create_directory, directory_tree, move_file, search_files, get_file_info, list_allowed_directories, delete_multiple_files, shell_exec), but descriptions lack LLM-optimization guidance and recovery hints.
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.
Delete multiple files in a single operation. This tool continues processing even if some files cannot be deleted, providing a detailed report of successes and failures for each file. Use with caution as deleted files cannot be recovered. Only works within allowed directories.
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). Supports optional 'depth' parameter (default: 1) to control recursion depth. The output is formatted with 2-space indentation for readability. Only works within allowed directories.
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.
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.
shell_exec tool has no visible input schema definition. Cannot verify parameter types, constraints, or descriptions. This is a critical gap for a high-risk tool (IRREVERSIBLE).
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., file paths, IDs). Violates pattern:tool and mxe:include-chaining-ids.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. LLMs cannot distinguish safe reads from destructive writes without explicit hints. Critical for delete_multiple_files and shell_exec.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2026-07-28+ | v2 |
Get the current operational mode of the server
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.
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 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.
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.
Set the operational mode of the server
Execute shell commands in the dev container environment
Write content to a file. Creates the file if it doesn't exist, or overwrites it if it does. Perfect for creating new files or replacing entire file contents. Only works within allowed directories.
Error handling is minimal. No recovery guidance, no actionable error messages, no categorization of retryable vs fatal errors. Violates pattern:recovery-guide and pattern:error-classification.
Parameter descriptions are sparse or missing. 'paths' in read_multiple_files and delete_multiple_files lack format/constraint details. 'pattern' in search_files lacks examples of valid patterns. Violates pattern:tool-description.