Cross-Platform Filesystem 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_platform_infoB | Get information about the current platform and allowed paths |
| list_directoryC | List contents of a directory |
| read_fileC | Read contents of a text file |
| write_fileC | Write content to a file |
| create_directoryC | Create a directory (and parent directories if needed) |
| delete_fileC | Delete a file |
| delete_directoryC | Delete a directory and its contents |
| move_itemC | Move or rename a file or directory |
| copy_itemC | Copy a file or directory |
| get_file_infoC | Get information about a file or directory |
| search_filesC | Search for files by name pattern |
| execute_commandC | Execute a shell command (platform-aware) |
| get_current_directoryA | Get the current working directory |
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 13 tools
Every tool has a clearly distinct purpose with no ambiguity. Each targets a specific filesystem operation (e.g., copy_item vs. move_item, delete_file vs. delete_directory, read_file vs. write_file), and the descriptions clearly differentiate them. An agent can easily distinguish between tools like get_file_info (metadata) and list_directory (contents).
Tool names follow a consistent verb_noun pattern throughout, using snake_case uniformly. Examples include copy_item, create_directory, delete_file, get_current_directory, and list_directory. This predictability makes the set easy to navigate and understand at a glance.
With 13 tools, the count is well-scoped for a cross-platform filesystem server. Each tool earns its place by covering essential operations like CRUD for files and directories, navigation, information retrieval, and utilities like search and command execution. It avoids bloat while providing comprehensive coverage.
The toolset offers complete CRUD/lifecycle coverage for the filesystem domain, including create (create_directory, write_file), read (read_file, list_directory, get_file_info), update (move_item, copy_item), and delete (delete_file, delete_directory). It also includes utilities like search_files, get_platform_info, and execute_command, ensuring no dead ends for agents.