filesystem-mcp
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 |
|---|---|
| list_filesC | List files/directories. Can optionally include stats and list recursively. |
| stat_itemsC | Get detailed status information for multiple specified paths. |
| read_contentC | Read content from multiple specified files. |
| write_contentC | Write or append content to multiple specified files (creating directories if needed). |
| delete_itemsC | Delete multiple specified files or directories. |
| create_directoriesC | Create multiple specified directories (including intermediate ones). |
| chmod_itemsC | Change permissions mode for multiple specified files/directories (POSIX-style). |
| chown_itemsC | Change owner (UID) and group (GID) for multiple specified files/directories. |
| move_itemsC | Move or rename multiple specified files/directories. |
| copy_itemsC | Copy multiple specified files/directories. |
| search_filesB | Search for a regex pattern within files in a specified directory (read-only). |
| replace_contentC | Replace content within files across multiple specified paths. |
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 12 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific filesystem operation (e.g., copy_items vs. move_items, read_content vs. write_content), and the descriptions clearly differentiate their functions. There is no overlap that would cause an agent to misselect between tools.
All tool names follow a consistent verb_noun pattern with snake_case throughout (e.g., list_files, create_directories, delete_items). The naming is predictable and readable, with no deviations or mixed conventions, making it easy for agents to understand and use the tool set.
With 12 tools, the count is well-scoped for a filesystem server, covering essential operations without being overwhelming. Each tool earns its place by addressing a core filesystem task, such as file management, content handling, and metadata operations, making the set comprehensive yet manageable.
The tool set provides complete coverage for filesystem operations, including CRUD/lifecycle functions (create, read, update, delete), file manipulation (copy, move), permissions (chmod, chown), and search capabilities. There are no obvious gaps, and agents can perform typical filesystem workflows without dead ends.