Local 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| disk_usageA | Calcule la taille totale d'un dossier en mégaoctets. Args: path: chemin local du dossier, ex: ~/Downloads |
| find_filesC | Cherche dans un dossier les fichiers dont le nom contient un mot-clé. Args: directory: dossier où chercher, ex: ~/Documents keyword: mot à trouver dans les noms de fichiers, ex: rapport |
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 2 tools
Both tools have clearly distinct purposes: one calculates folder size, the other searches for files by name. There is no overlap or ambiguity.
Both use snake_case, but disk_usage is noun_noun while find_files is verb_noun, showing a minor inconsistency in pattern.
Only 2 tools for a file system server is too few; essential operations like listing, reading, writing, deleting files are missing, making the tool set feel incomplete.
The tools cover only disk usage and file search, leaving out basic file CRUD operations, which are necessary for a file system utility.