MCP Filesystem Python
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| directory | Yes | Path to the directory to serve files from |
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 |
|---|---|
| search-filesA | Search for files containing specific text |
| write-fileB | Write content to a file |
| delete-fileB | Delete a file or directory |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-file | Get a summary analysis of a file's contents |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| uv-1c83b73deef05048.lock | File: uv-1c83b73deef05048.lock |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: deleting, searching, and writing files. No overlap or ambiguity.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., delete-file, search-files). No mixing of conventions.
With only 3 tools, the server is on the lower end of the ideal range. While each tool is distinct, the count feels thin for a filesystem server.
Fundamental operations like reading file content or listing directories are missing. Agents cannot perform basic file access, leading to significant gaps.