MCP File System
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileD | – |
| read_multiple_filesD | – |
| write_fileD | – |
| create_directoryD | – |
| list_directoryD | – |
| move_fileD | – |
| get_file_infoD | – |
| list_allowed_directoriesD | – |
| search_filesD | – |
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 9 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools like create_directory, list_directory, read_file, write_file, move_file, and search_files all target specific file system operations without overlap. Even read_file and read_multiple_files are clearly differentiated by single vs. batch operations.
All tools follow a consistent verb_noun pattern using snake_case throughout. Examples include create_directory, list_directory, read_file, write_file, move_file, search_files - this predictable naming makes the toolset easy to navigate and understand.
With 9 tools, this is well-scoped for a file system server. Each tool earns its place by covering essential operations: directory management, file reading/writing, file operations, and searching. The count is neither too sparse nor overwhelming for the domain.
The toolset provides excellent coverage of core file system operations including CRUD-like functionality (create, read, write, move) and directory operations. The only minor gap is the absence of delete operations (delete_file, delete_directory), but agents can work around this limitation for most workflows.