PCB Weaver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_engineering_jobC | Queue a persistent job for the workbench or standalone worker. This MCP session never owns its execution. |
| get_engineering_jobB | Read actual engineering stages, outcomes and evidence from a durable job. |
| list_engineering_jobsA | List up to 100 lightweight job summaries. Use get_engineering_job for full steps and native evidence. |
| cancel_engineering_jobA | Request cancellation at the next stage boundary; does not kill an active native EDA operation. |
| environment_statusB | Discover actual local KiCad, native Python bridge and Java/router capabilities. |
| import_pcb_projectB | Snapshot a KiCad board and project sidecars. Use parent_revision for an external ECO revision. |
| inspect_pcb_revisionB | Read the revision's actual components, nets, outline, restrictions and constraints. |
| inspect_pcb_inventoryB | Read revision-bound component, pin, network and copper data. Page until total is exhausted; missing metadata and unverified connectivity stay explicit. |
| list_pcb_revisionsB | List known immutable revisions in creation order. |
| set_design_constraintsB | Create a child revision containing validated design intent and compiled KiCad minima. |
| propose_pcb_layoutsC | Run deterministic numerical placement optimization; compare measured feasible candidates. |
| apply_pcb_layoutC | Apply one recorded feasible placement plan into a new board revision and audit the result. |
| autoroute_pcb_revisionB | Export DSN, run local Freerouting and import SES through KiCad. Unrouted supported boards only. |
| diagnose_pcb_repairB | Read recorded verified DRC findings and scoped repair proposals. Does not run native tools. |
| submit_pcb_repairC | Queue scoped repair with explicit nets, ROI and approved copper removal IDs. Never releases manufacturing files. |
| submit_pcb_auto_repairA | Queue automatic target discovery, bounded proposals and native checks. No coordinates required. Default additive-only; optional neckdown/fanout require explicit options. Never manufactures. Read job detail for the retained revision and retry from it. |
| submit_pcb_reference_repairB | Queue local multi-net ECO repair using an explicit compatible, natively verified reference. Preserves source rules/placement and adopts only native improvements. Not whole-board replacement or manufacturing authorization. |
| submit_pcb_completionA | Queue bounded layout candidates, whole-board routing, native checks and automatic repair. Unrouted inputs only; no manufacturing authorization. Poll engineering job for actual attempts and the best review revision. |
| submit_pcb_clearance_repairC | Queue bounded F.Cu joint movement in an explicit ROI. Keeps widths/vias/pads; fresh native gates reject regressions. Never releases. |
| verify_pcb_revisionB | Run real ERC/DRC, schematic connectivity and geometric checks with revision-bound evidence. |
| analyze_pcb_ecoC | Compare connectivity, placement and project-file changes; identify changed nets for review. |
| build_pcb_manufacturing_releaseB | Reverify, export actual manufacturing files and create a hash-manifest ZIP only on success. |
| verify_pcb_release_archiveB | Verify a release ZIP's exact file set and all SHA-256 values without extracting it. |
| pcb_project_historyB | Read and validate the project's local hash-chained operation ledger. |
| export_pcb_review_reportB | Generate a self-contained HTML review with actual board geometry and verification evidence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| pcb_engineering_workflow |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| integration_contract | The actual local machine bridge contract, not a corporate compatibility certificate. |
| constraints_schema |
TDQS
Scored across 25 tools
Most tools map to distinct lifecycle stages, but the set has six repair/layout submission tools (submit_pcb_repair, submit_pcb_auto_repair, submit_pcb_reference_repair, submit_pcb_clearance_repair, submit_pcb_completion, propose/apply_layout) that could easily be misselected. Descriptions do clarify scope and explicitly disclaim adjacent capabilities, but the overlap is substantial enough to create real ambiguity.
Nearly all tools follow a lowercase snake_case verb_noun pattern (list_engineering_jobs, verify_pcb_revision, build_pcb_manufacturing_release). A few break the verb-first pattern (environment_status, pcb_project_history) and the pcb_ infix is not perfectly uniform, but the overall convention is clear and predictable.
25 tools is heavy for a single MCP server, and the repair family in particular contains several variants that could be consolidated behind a mode parameter. The complex PCB lifecycle justifies breadth, but the current count sits at the upper boundary where each tool is not obviously earning its place.
The surface covers the core PCB lifecycle well: import, revision inspection, constraints, layout, autorouting, multiple repair modes, verification, release build/verify, and review export. Minor gaps remain around creating a design from scratch, BOM/component editing, and direct schematic manipulation, but these are workable for the stated automation purpose.