Proposed edits
The AI proposes, and nothing is saved untested. Through the MCP server, an assistant works out a change with propose_edits and sees its effect on the checks. On the local server nothing reaches your files until apply_edits runs on a proposal you agreed to; on the hosted server it is saved as a new revision.
Two steps
Every change to a project goes through two tools of the MCP server. The others only read the design.
propose_editschecks the changes against the design and runs them on a copy of the files. Nothing is written. It analyses the result and returns a proposal id with what would change:- the parts and nets affected;
- ERC, DRC, parity and unrouted counts, before and after;
- the check results the change would add (
newIssues) or resolve (resolved).
apply_editswrites a proposal you have agreed to. It is the only tool that writes. MCP clients see it marked as destructive, so they ask you before running it.
Read the proposal before you say yes. If the before and after counts show a new error, ask the assistant for a different change.
What can be changed
The set of edits is deliberately small and low-risk for now.
| Change | What it does |
|---|---|
set_field |
Sets a field on every unit of a part: Value, Footprint (Library:Name), Datasheet, MPN or any other. A new value is carried to the board footprint too, as Update PCB from Schematic would. A new footprint is not: the proposal shows the parity error that leaves, which you fix with Update PCB in KiCad. |
no_connect |
Puts a no-connect flag on an unused pin. Refused if the pin is connected or already flagged. |
annotate |
Numbers the unnumbered parts (R?), or all of them again. |
refill_zones |
Refills the board's copper zones. |
move_part |
Moves a footprint to a position, turns it, or both. The tracks of its nets come off and are routed again; the rest of the board stays as it was. A move onto another part is refused. If the board was built from a design spec, the spec then keeps the part there. |
Adding or removing parts and changing connections go through the design spec of a board that was built from requirements: the assistant changes the spec and builds again.
Backups and how files are written
Before apply_edits replaces a file, it copies it to .crossprobe/backups/<time>/ in the project folder. To undo an applied edit, copy the files back from there.
Each file is written under a temporary name and then renamed over the original.
When files changed after the proposal
apply_edits writes only if the project files are exactly as they were when the proposal was made. If you saved something in KiCad in the meantime, it refuses and asks for a new proposal. Ask the assistant to propose the change again; the new proposal is worked out from the files as they are now.
The server also checks the project files' size and modification time before each answer, and analyses the project again when something changed. The assistant's answers follow what you save in KiCad.
After an edit
If the project is open in KiCad when an edit is applied, reload it there. Run ERC and DRC as usual; the written schematic and board are checked in Crossprobe's tests to pass KiCad's own ERC and DRC parity.
On the hosted server
The hosted server works on projects stored in your account. There the assistant applies the change you asked for without asking again, because a save is a new revision and the earlier ones are kept: nothing is overwritten, and an unsaved proposal would not show in the app at all. There are no backup files; open an earlier revision from the project menu to go back. A project that was saved in between makes the proposal stale, as on the local server.
In the browser app
These edits are available through the MCP server only. The AI review in the app reads the design and reports findings; it does not offer fixes yet. See what the review checks, and the tools reference for the inputs of propose_edits and apply_edits.