FileMCP
Related Servers
Alternatives to FileMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides secure access to local file system operations.MIT
- AlicenseAqualityAmaintenanceFilesystem MCP server for AI assistants. Search, read, edit, and manage local files in directories you choose.6142,827 npm32MIT
- FlicenseBqualityDmaintenanceA lightweight MCP server for basic file operations, enabling reading, writing, and listing files securely via the Model Context Protocol.31-
- FlicenseCqualityDmaintenanceAn MCP server for reading files from the local filesystem. Currently supports listing files in directories on the Desktop.3-
- AlicenseNot gradedqualityBmaintenanceA local filesystem MCP server providing constrained file operations (read/write, directory management, search, metadata) within configurable directories, with read-only mode and zero runtime dependencies.4 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes file operations (list, read, write, delete, unzip) in a sandbox directory, preventing path traversal.7 npmMIT
TDQS
Scored across 5 tools
createFileTool and overwriteFileTool both write name+content to a file and their descriptions do not clarify behavior when the file already exists, creating a mild risk of misselection. The other three tools (createDirectoryTool, readFileTool, listDirectoryTool) are clearly distinct in purpose, so overlap is limited to one pair.
All tools follow a strict verb_noun pattern in camelCase with the same 'Tool' suffix (createFileTool, overwriteFileTool, createDirectoryTool, readFileTool, listDirectoryTool). The naming is highly predictable and self-documenting.
Five tools is well-scoped for a sandboxed file-operation server: create file, overwrite file, create directory, read file, and list directory. Each tool covers a distinct capability and none feels redundant or excessive.
The surface covers create, read, list, and overwrite, but there is no delete operation for files or directories, and no move/rename or metadata/existence check. These are notable gaps for a file-management domain, though agents can partially work around the missing overwrite-as-update behavior.