version: "1.0.1" name: easyeda-copilot-mcp description: Create, modify, place, route, or review EasyEDA schematics and PCBs with EasyEDA Copilot MCP tools. Supports independent schematic, placement, mechanics, routing, and verification tasks.

EasyEDA Copilot MCP

Complete only the stage requested by the user. A schematic task does not authorize PCB work; placement does not authorize routing.

Start

1. If multiple EasyEDA windows may be connected, call list_easyeda_instances and select the intended instance.
2. Call get_all_projects when the project is unknown and switch with open_document({ project_uuid }); it saves all open design tabs before switching. Then call get_current_project_info once when the document tree or exact document is unknown.
3. Select one task mode below and read only its references.
4. Open the exact schematic page or PCB before inspecting or changing it.

Required behavior

• New or substantially expanded schematics must use functional EasyEDA schematic pages.
• beautify_schematic_on_current_page rebuilds the entire current page. Every current-page component must appear in exactly one functional block.
• After import_pcb_changes, stop and ask the user to confirm the EasyEDA import dialog. Do not continue until the user says it is complete.
• Open the target PCB before make_pcb_layout; this supplies its outline and component positions to preserve(...).
• Treat placement and routing as one coupled physical problem: plan plausible signal, power, return, escape, and thermal paths before placement, then verify placement feasibility before routing. High density is valid when the intended layer and via strategy supports it.
• Placement preview is not applied. Assemble only a completed final layoutId, after user approval.
• Long placement and routing calls are complete only after wait_operation returns a terminal result. If calculation finished but applying its saved in-memory result failed, retry it with apply_operation instead of rerunning the calculation.
• Existing PCB copper and objects are preserved by placement assembly. Existing routing is preserved by the router unless clearRouting(...) explicitly selects copper to replace.
• For stack-dependent routing intent, use verified physical data, declare and report a reasonable provisional stack, or ask for the missing data. Do not silently omit the semantic constraint.
• After verification, decide whether to keep, repair, or restore the agent-applied result. Prefer a focused repair for a local error; restore a clearly invalid or broadly regressed result that cannot be repaired safely. Do not restore for a warning alone, and report the decision.

Finish

Report changed documents, checks performed, unresolved findings, and the next requested stage. Do not suggest work beyond the user's requested boundary.