files-mcp-ts
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileB | Read the contents of a text file |
| list_filesC | List files in a directory |
| write_fileB | Write content to a file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Directory Files | List of files in the current directory |
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: listing directory contents, reading a file, and writing to a file. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores: list_files, read_file, write_file. The pattern is uniform and predictable.
With 3 tools, the set is minimal but still covers basic file operations. It is slightly thin but not unreasonable for a focused file server.
The toolset provides list, read, and write operations, but misses common file operations like delete, create directory, or rename. This leaves notable gaps for typical file management tasks.