SolidCraft MCP Not Working? Fix Claude Tool Call Errors
▶ Watch on YouTube & subscribe to The Stack Underflow
When Claude and SolidCraft won’t work together, check from the wall outward, like a lamp that won’t light: is the plug listed, does it connect, is SolidCraft’s window open, and what does the reply actually say? Each stop has its own error words. Find yours below.
The one-line version: read the exact error words, find the stop they belong to, and fix only that stop.
Last verified in our lab: 30 October 2026 (SolidCraft 0.27.0; Claude Code 2.1.311, with Claude Sonnet 5.5 for the two Claude turns; Linux in Docker). The other errors come from a test script with no AI, sending the same tool calls a Claude app sends.
The words first
- Plug (MCP server): the small program,
solidcraft-cli mcp, that lets a Claude app use SolidCraft’s tools. Lesson 1 sets it up. - PATH: the list of folders your computer searches when a command is given by its short name.
- Headless session: SolidCraft working with no window, so you can’t see what was built.
- Batch: several steps sent at once. If one fails, the whole batch is undone (rolled back).
Stop 1: is the plug listed?
In a terminal (not Claude’s chat box): claude mcp list. Inside Claude Code: /mcp. In Claude Desktop: the + button under the chat box, then Connectors.
No MCP servers configured. Use `claude mcp add` to add a server.
Fix: in SolidCraft, the round ? button (top right), Connect AI assistants. It says “Restart each assistant to load the SolidCraft server.” Restart Claude (Claude Desktop: quit it completely, then open it again). In our test of 0.27.0 it did not add itself in 30 seconds, though its guide says it does.
Stop 2: does it connect?
solidcraft-cli mcp - Failed to connect — ENOENT: Executable not found in $PATH: "solidcraft-cli"
The plug was added by its short name (claude mcp add --scope user solidcraft -- solidcraft-cli mcp) on a computer whose PATH doesn’t include SolidCraft’s folder. Fix: Connect AI assistants again. It says “claude-code: updated the path of solidcraft” and writes the full path.
Stop 3: is SolidCraft’s window open?
Every reply ends: “Note: this is a headless session because the SolidCraft app was not found; the user cannot see this work. …”
- Nothing built yet: open SolidCraft and ask again. Claude did exactly that in our run.
- Something already built hidden: open SolidCraft, then quit and reopen your Claude app. The new session starts empty, so build it again.
- SolidCraft closed mid-session: “did not answer (connection closed)”, then “no SolidCraft app is listening”. Open it, and check the design before sending a change.
Stop 4: what does the reply say?
A typo in a batch:
"failed": {"index": 1, "error": "expression: unknown parameter `hook_dept`"}, "rolled_back": true
Index 1 is the second step (counting from 0). The step that ran was undone: 8,500 mm³ before and after. Fix the name and send it again.
A save outside the plug’s folders: “outside the folders this agent may use (…); allow another folder with --allow-path DIR”. Fix in Claude Code:
claude mcp remove solidcraft -s user
claude mcp add --scope user solidcraft -- FULL-PATH-OF-solidcraft-cli mcp --allow-path YOUR-FOLDER
The full path is the one claude mcp list showed. In Claude Desktop’s settings file, the arguments become:
"args": ["mcp", "--allow-path", "YOUR-FOLDER"]
Restart. After that edit, Connect AI assistants says “solidcraft left as you have it (it is not a plain SolidCraft entry)”, so after an update, check the path yourself with claude mcp list.
A file from a newer SolidCraft: “this design was saved by a newer SolidCraft (file format 44; this version reads formats up to 43): update SolidCraft to open it”.
What Claude did
One run, with what we expected written down before it ran. With SolidCraft closed it said “a new, untitled headless one, not your app … Start SolidCraft with your design open and ask me again”. With SolidCraft open, its next call reached the window. The save to Documents was refused with the same words as above, and Claude said to add --allow-path and restart. It saved nothing elsewhere.
Filmed in Claude Code’s manual mode (its default is auto). Commands were typed by a script.
The course
- Previous: Lesson 6: edit a model with Claude without breaking it
- Next: Lesson 8: assembly, a hook that slides on a rail
- The lab for this lesson, with every error message: solidcraft-course-lab/out/l7
Sources
- The lab: the test script, logs and the exact text of every error above
Change notes
- 16 Nov 2026: first published, from the lesson’s lab results of 30 Oct 2026.
Not affiliated with or endorsed by SolidCraft (Tangency Labs) or Anthropic. Found a mistake? Tell us in the video’s comments and we’ll correct this page.
Found this useful? The deep version lives on YouTube — new breakdowns of how AI dev tools actually work, weekly.
Subscribe on YouTube →Prefer email? Get the free newsletter: one failure, traced step by step, about once a week.