AI FileSystem MCP

transaction

Apply a batch of file create/write/update/move/delete operations atomically. If any operation fails, all prior operations are reverted from backups.

Instructions

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operations`	Yes	Ordered list of file operations to execute as one atomic batch.
`rollbackOnError`	No	When true (default), any failure rolls all completed ops in the batch back from backup.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv4.0.0May 25, 2026

changedInput schema / properties / operations / description

Previous value: -"List of file operations to execute"New value: +"Ordered list of file operations to execute as one atomic batch."

addedInput schema / properties / operations / items / additionalProperties
```
Added value: +false
```

changedInput schema / properties / operations / items / properties / content / description

Previous value: -"Content for create/update operations"New value: +"Required for \"create\" and \"write\"."

addedInput schema / properties / operations / items / properties / destination

Added value: +{
+  "description": "Required for \"move\" (new path).",
+  "type": "string"
+}

removedInput schema / properties / operations / items / properties / encoding

Removed value: -{
-  "default": "utf8",
-  "description": "File encoding",
-  "type": "string"
-}

changedInput schema / properties / operations / items / properties / path / description

Previous value: -"File path for the operation"New value: +"Target file or directory path."

changedInput schema / properties / operations / items / properties / type / description

Previous value: -"Type of operation"New value: +"Operation kind. create=new file, write=overwrite, update=text replace, move=rename, delete=remove."

changedInput schema / properties / operations / items / properties / type / enum

Previous value: -[
-  "create",
-  "read",
-  "update",
-  "delete"
-]New value: +[
+  "create",
+  "write",
+  "update",
+  "move",
+  "delete"
+]

addedInput schema / properties / operations / items / properties / updates

Added value: +{
+  "description": "Required for \"update\". Each entry is { oldText, newText } and is applied in order via string replace.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "newText": {
+        "type": "string"
+      },
+      "oldText": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "oldText",
+      "newText"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / operations / minItems
```
Added value: +1
```

changedInput schema / properties / rollbackOnError / description

Previous value: -"Whether to rollback all operations if any fails"New value: +"When true (default), any failure rolls all completed ops in the batch back from backup."

First observedv2.0.0Feb 9, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Disclosures atomicity, rollback on failure, and default behavior of rollbackOnError. No annotations provided, so description carries full burden; it adequately informs about core behavior but does not mention success outcomes or side effects beyond rollback.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with the core purpose, followed by a key differentiator. No superfluous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (two parameters, one nested array) and no output schema, the description covers atomicity, rollback, and operation types adequately. Lacks explanation of return value or error handling details, but the core use case is clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents parameters fully. The description adds minimal extra context (e.g., 'from on-disk backups') but does not significantly enhance understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'apply', resource 'batch of file operations', and atomicity. Distinguishes from the agent's built-in Edit by noting this is something it cannot do, providing sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts with the agent's per-file Edit, implying when to use this tool (for atomic batch operations). Lacks explicit when-not-to-use or alternatives beyond that single comparison.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

transactionA