FileMCP
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| createFileToolC | Creates a file with the specified name and content. |
| overwriteFileToolB | Overwrites a file with the specified name and content under 'AgentFiles'. |
| createDirectoryToolB | Creates a directory with the specified name. The directory will be created inside the 'AgentFiles' directory. |
| readFileToolA | Reads a file from the 'AgentFiles' directory and returns its contents as text. |
| listDirectoryToolB | Lists files and folders in a directory under 'AgentFiles'. |
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 5 tools
createFileTool and overwriteFileTool both write name+content to a file and their descriptions do not clarify behavior when the file already exists, creating a mild risk of misselection. The other three tools (createDirectoryTool, readFileTool, listDirectoryTool) are clearly distinct in purpose, so overlap is limited to one pair.
All tools follow a strict verb_noun pattern in camelCase with the same 'Tool' suffix (createFileTool, overwriteFileTool, createDirectoryTool, readFileTool, listDirectoryTool). The naming is highly predictable and self-documenting.
Five tools is well-scoped for a sandboxed file-operation server: create file, overwrite file, create directory, read file, and list directory. Each tool covers a distinct capability and none feels redundant or excessive.
The surface covers create, read, list, and overwrite, but there is no delete operation for files or directories, and no move/rename or metadata/existence check. These are notable gaps for a file-management domain, though agents can partially work around the missing overwrite-as-update behavior.