High-Performance File System MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileB | Read the complete content of a single text file. |
| read_multiple_filesA | Read the contents of multiple files in a single request. |
| write_fileA | Create a new file or overwrite an existing file with text content. |
| edit_fileA | Update an existing file by replacing target text with new text. |
| delete_fileB | Delete a specific file from the filesystem. |
| create_directoryA | Create a directory path recursively. |
| list_directoryA | List all items inside a directory with metadata (size, isDirectory, modified date). |
| delete_directoryB | Delete a directory and optionally all of its contents. |
| move_fileA | Move or rename a file or directory. |
| get_file_infoA | Get metadata for a file or directory (size, modification date, path stats). |
| search_filesB | Search for files within a directory matching a glob pattern. |
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 11 tools
Each tool targets a distinct operation: read vs. read_multiple, write vs. edit, file vs. directory actions. get_file_info and list_directory might seem similar, but descriptions clarify that one returns metadata for a single path while the other lists directory contents.
Most tool names follow a verb_noun pattern (read_file, write_file, delete_file, create_directory). Minor deviations include read_multiple_files (verb_phrase) and get_file_info (uses 'get' instead of 'read'), but the overall convention is consistent and readable.
With 11 tools, the set is well-scoped for a file system MCP server. Each tool covers a necessary file or directory operation without unnecessary redundancy or bloat.
The tool surface covers core lifecycle operations for files and directories: create, read, update, delete, list, move, and search. A notable gap is the lack of a copy operation, but move_file and edit_file cover most workflows.