transactionLABSCO SUMMARY
Reach for it only when half-applied is worse than not applied.
The README is unusually clear about when not to use this — a single-file edit belongs in the agent's own edit tool, and a one-liner belongs in the shell. Where it earns its place is a change that has to land together: a schema file with its ORM model and fixtures, or a routing entry with its handler, where the intermediate state is broken code.
What it is
A deliberately single-purpose MCP server. Coding agents already read, write, edit and grep well; what they lack is a primitive for "apply these N file changes together, or none of them." That gap is the entire job here — earlier 2.x versions shipped 39 commands and the project cut them because the agent's own tools do that work better.
What you get
transaction— a list ofoperationsplusrollbackOnError, applied in order- Five operation kinds:
createa new file with parent directories,writeto overwrite an existing one,updatefor in-place text replacements applied in order,moveto rename,deletefor a file or directory - Real rollback — if the fourth operation fails, the first three are restored from backup before the call returns; on success the backups are cleaned up
Requirements
No account and no key. Node.js ≥ 18. Clone it and npm run build, then point the client at dist/index.js. Speaks stdio JSON-RPC with no network ports. There is no path sandbox: it runs as the user who started it and the trust boundary is the machine, so keep it beside an agent you trust and do not expose it to other clients. The manifest calls the package ai-filesystem-mcp at 4.0.0, MIT, a name npm does not have.
Setup effort
Build from source — git clone https://github.com/proofmath-owner/ai-filesystem-mcp.git
USE CASES
01
Landing a migration across three files
Put the schema change, the model update and the fixtures in one transaction so a failure leaves nothing half-written.
02
Renaming something across many files
Batch the replacements so an agent that runs out of context mid-stream does not leave the repository in an inconsistent state.
03
Keeping generated and hand-written code in step
Write the generator output and the glue that depends on it together, or not at all.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/proofmath-owner/ai-filesystem-mcp.git
cd ai-filesystem-mcp
npm install
npm run build
node dist/index.jsMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"ai-filesystem": {
"command": "node",
"args": [
"<YOUR_PATH_TO_AI_FILESYSTEM_MCP>/dist/index.js"
]
}
}
}
