MCP File Manager
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_filesA | |
| read_fileB | |
| file_infoA | |
| search_filesA | |
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
Each tool targets a distinct file operation: listing directory contents, reading file content, fetching metadata, and searching filenames. There is no overlap, so an agent can easily choose the right tool.
Three tools use the verb_noun pattern (list_files, read_file, search_files), but file_info is a noun phrase rather than a verb action. The naming is mostly consistent but has a minor deviation.
Four tools is a well-scoped number for a focused file management server. Each tool serves a clear purpose without unnecessary bloat.
The server only provides read-only operations (list, read, info, search). There are no tools for creating, editing, or deleting files, which are essential for a true file manager, leaving significant gaps.