DNA News

Act on this, mostly signal

SolidCraft MCP rolls back a failed batch across all steps

What to do

Test MCP edits with a failing step to confirm the server rolls back cleanly.

Why

The author's Docker lab found a failed batch undoes every step and the file sandbox is on by default.

Read the source at reddit.com

What the research found

Author's Docker lab tests SolidCraft v0.14.0 MCP server: failed batch rolls back all steps, set_parameter recomputes cleanly, file sandbox is on by default, and Claude Code finished in 13 calls with no failures. Results are from the author's own test client and video channel.

Claims and how well the evidence supports them

  1. SolidCraft v0.14.0 MCP server rolled back a failed 13-command batch, returning rolled_back true and undone 3 (jev unclear) 56%
  2. A set_parameter call changed width from 80 to 100 mm and recomputed without errors 99%
  3. The MCP file sandbox is on by default and --allow-any-path removes it 99%
  4. Claude Code completed the task in 13 tool calls with none failing in about 35 seconds 99%

Evidence

Actionability rated medium.