emperor-folder
Related Servers
Alternatives to emperor-folder
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables secure filesystem operations (read, write, list, move, search files/directories) through the Model Context Protocol, with dynamic directory access control via MCP Roots.-
- FlicenseNot gradedqualityDmaintenanceMCP server for filesystem operations, enabling reading, writing, editing, moving, and searching files with dynamic directory access control via MCP Roots.1,304,784 npm-
- AlicenseNot gradedqualityBmaintenanceEnables agents to safely read, write, edit, move, list, and search files and directories within explicitly allowed root paths, refusing escapes via parent segments or symlinks.342 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse selected folders, search filenames, inspect metadata, and read bounded UTF-8 text files through a read-only, token-authenticated interface.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables remote filesystem access and command/process control through MCP, with safe-by-default permission profiles that restrict file operations to configured roots and make command execution an explicit opt-in.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to browse and search folders, find files, list albums, read file contents, and retrieve item metadata or storage quota in a read-only manner.-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list enumerates directory contents, read returns file contents, search finds regex matches, and stat describes metadata. There is little risk of confusing these operations, even though list and search can both traverse folders.
All four tools use short, lowercase verb-style names with a consistent convention. The pattern is predictable and readable throughout the set.
Four tools are well-scoped for a folder/filesystem inspection server. Each tool covers a distinct core operation without unnecessary bloat.
The surface covers read-only filesystem workflows well: listing, reading, searching, and metadata inspection. If write operations such as create, delete, or move are expected for a folder server, those are missing, but the read-only scope appears intentional.