MCP Filesystem Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_ALLOWED_DIRS | No | Colon-separated list of allowed directories (alternative to positional CLI 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_fileA | Read the complete contents of a file. |
| read_multiple_filesB | Read multiple files at once. |
| write_fileA | Create a new file or overwrite an existing file with new content. |
| create_directoryA | Create a new directory or ensure a directory exists. |
| list_directoryA | Get a detailed listing of files and directories in a path. |
| move_fileC | Move or rename files and directories. |
| get_file_infoC | Retrieve detailed metadata about a file or directory. |
| list_allowed_directoriesC | Returns the list of directories that this server is allowed to access. |
| edit_fileA | Make line-based edits to a text file. |
| head_fileA | Read the first N lines of a text file. |
| tail_fileA | Read the last N lines of a text file. |
| search_filesA | Recursively search for files and directories matching a pattern. |
| directory_treeA | Get a recursive tree view of files and directories. |
| calculate_directory_sizeB | Calculate the total size of a directory recursively. |
| find_duplicate_filesA | Find duplicate files by comparing file sizes and contents. |
| compare_filesB | Compare two text files and show differences. |
| find_large_filesB | Find files larger than the specified size. |
| find_empty_directoriesC | Find empty directories. |
| grep_filesA | Search for pattern in files, similar to grep. |
| read_file_linesA | Read specific lines from a text file. |
| edit_file_at_lineA | Edit specific lines in a text file. |
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 21 tools
Each tool has a clearly distinct purpose with minimal overlap. For example, read_file reads entire files while head_file reads first lines, and edit_file makes line-based edits while edit_file_at_line targets specific lines. The find_* tools (duplicate_files, empty_directories, large_files) each target different search criteria, preventing confusion.
All tools follow a consistent verb_noun naming pattern with snake_case throughout. Examples include calculate_directory_size, compare_files, create_directory, and list_directory. There are no deviations in naming conventions, making the tool set predictable and easy to understand.
With 21 tools, the count is slightly high but reasonable for a filesystem server covering a broad range of operations. It includes core file operations (read, write, move), directory management, search utilities, and specialized tools like duplicate detection. While comprehensive, it might feel heavy but remains well-scoped for the domain.
The tool set provides complete coverage for filesystem operations, including CRUD (create_directory, write_file, read_file, move_file, delete implied via move/overwrite), search (grep_files, search_files), metadata (get_file_info), and utilities (compare_files, edit_file). There are no obvious gaps, and tools support common workflows like file editing, directory traversal, and content analysis.