AI FileSystem MCP
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transactionA | Apply a batch of file create/write/update/move/delete operations atomically. If any operation fails (and rollbackOnError is true, the default), all prior operations in the batch are reverted from on-disk backups. This is the one thing the agent's built-in per-file Edit cannot do. |
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 1 tool
With only one tool, there is no ambiguity between tools. The single tool has a clearly defined purpose.
With a single tool, naming is trivially consistent. The name 'transaction' is descriptive and fits the tool's purpose.
A single tool for a file system server is too few. The server's purpose implies a need for multiple operations, but only a batch transaction tool is provided.
The server severely lacks basic file operations (read, write, list, etc.). It only offers a batch transaction tool, which is a narrow supplement, not a complete file system interface.