file-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_FILE_ROOT | No | Root directory lock. All operations are resolved and validated against this root. Defaults to the current directory. Multiple roots can be separated by ':' (Linux/macOS) or ';' (Windows). | |
| MCP_WRITE_ENABLED | No | Set to 0 to disable all write operations. | 1 |
| MCP_ALLOW_HARDLINKS | No | Set to 1 to allow hardlinks, disabling the st_nlink > 1 hardlink escape check. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dirB | 列出目录内容(最多 500 项)。返回名称/类型/大小/修改时间。 |
| read_fileB | 读取文本文件内容(上限 1MB / 2000 行,自动识别二进制)。 |
| write_fileB | 写入文本文件(新建或覆盖;append=true 追加)。仅限根目录内。 |
| searchC | 在根目录内搜索:name_glob 按文件名匹配,content_regex 按内容正则匹配。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
list_dir, read_file, write_file, and search each target a clearly distinct operation (listing, reading, writing, searching) with no functional overlap. The only potential confusion is search's name_glob versus list_dir, but the descriptions make the boundary clear (global search vs. single-directory listing).
Three tools follow a clean verb_noun pattern (list_dir, read_file, write_file), while 'search' is a bare verb, a minor deviation from the otherwise consistent convention. Still highly readable and predictable.
Four tools cover core file operations without redundancy, and each earns its place. It is on the lean side for a 'file-manager' but still within a reasonable scope.
Core read, write, list, and search are covered, but a file manager is missing delete, move/rename, and copy/mkdir operations. These are notable gaps that limit real management workflows.