Proposed edits
Your assistant proposes, and nothing is saved untested. It works out a change with propose_edits and sees its effect on the checks, then saves it with apply_edits as a new revision of the project. The earlier revisions are kept.
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_editssaves the proposal as a new revision of the project.
The assistant applies the change you asked for without asking again: a save is a new revision and the earlier ones are kept, so nothing is overwritten, and an unsaved proposal would not show in the app at all. If the before and after counts show a new error, ask the assistant for a different change, or open the earlier revision from the project menu.
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.
Revisions
Each applied change is a revision of the stored project, marked as made by an assistant, with its reason. The last 50 are kept. To undo a change, open the revision before it from the project menu and save.
When the project changed after the proposal
apply_edits saves only if the project is at the revision the proposal was worked out from. If you, or another assistant, saved in the meantime, it refuses and the change is proposed again from the project as it is now.
If the project is open in the app when a change is saved, the app tells you the next time its tab gets focus and offers to load the new revision. Unsaved changes of your own are kept, and you choose.
The local server only reads a project and has neither tool.
See the tools reference for the inputs of propose_edits and apply_edits.