Skip to main content
Glama
Avinash1286

KiCAD MCP Server

by Avinash1286

Edit Schematic Component

edit_schematic_component
Destructive

Update KiCAD schematic component properties: change footprint, value, reference, reposition labels, and add/remove custom BOM attributes like MPN or supplier part numbers.

Instructions

Update properties of a placed symbol in a KiCAD schematic (.kicad_sch) in-place.

Use this tool to: • assign or update the footprint, value, or reference designator, • reposition field labels (Reference / Value text), • add, update, or remove ARBITRARY CUSTOM PROPERTIES used by BOM and sourcing workflows: MPN, Manufacturer, Manufacturer_PN, Distributor, DigiKey, DigiKey_PN, Mouser_PN, LCSC, JLCPCB_PN, Voltage, Tolerance, Power, Dielectric, etc.

Custom properties are first-class — they survive ERC, are exported by export_bom, and are picked up by the JLCPCB / Digi-Key BOM tooling. Newly-added properties default to hidden so they do not clutter the schematic canvas.

Multiple updates can be batched in a single call: pass any combination of footprint, value, newReference, fieldPositions, properties, and removeProperties together.

This is more efficient than delete + re-add because it preserves the component's position and UUID. Operates on .kicad_sch files only — to modify a PCB footprint use edit_component instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNoNew value string (e.g. 10k, 100nF)
footprintNoNew KiCAD footprint string (e.g. Resistor_SMD:R_0603_1608Metric)
referenceYesCurrent reference designator of the component (e.g. R1, U3)
propertiesNoAdd or update component properties. Map of property name to either a string value (sensible defaults) or a full spec object {value, x?, y?, angle?, hide?, fontSize?}. Use this to attach BOM and sourcing metadata such as MPN, Manufacturer, Distributor, DigiKey, LCSC, JLCPCB_PN, Voltage, Tolerance, Dielectric, Power, etc. Built-in fields (Reference, Value, Footprint, Datasheet) can also be set this way but the dedicated parameters above are clearer. Example: {"MPN": "RC0603FR-0710KL", "Manufacturer": "Yageo", "Tolerance": "1%"}
newReferenceNoRename the reference designator (e.g. R1 → R10)
schematicPathYesPath to the .kicad_sch file
fieldPositionsNoReposition field labels: map of field name to {x, y, angle, justify?} (e.g. {"Reference": {"x": 12.5, "y": 17.0, "justify": "left"}})
removePropertiesNoList of custom property names to delete from this component. The built-in fields Reference, Value, Footprint, and Datasheet cannot be removed (clear them by setting value to "" instead). Example: ["OldMPN", "Distributor_PN"]

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds significant context beyond the annotations: custom properties are first-class (survive ERC, exported by export_bom, used by BOM tooling), newly-added properties default to hidden, and batching preserves component position and UUID. The description is consistent with destructiveHint=true and readOnlyHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear opening sentence, bullet-point use case list, and short paragraphs for custom properties, batching, and file-type constraints. Every sentence earns its place and there is no fluff or repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 8 parameters and nested objects, the description covers purpose, usage, custom property semantics, batching, and the file-type limitation. Since an output schema exists, return values need not be detailed. The combination of description and schema is fully sufficient for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter in detail. The description adds value by explaining that parameters can be batched together and clarifying the purpose of custom properties, but it does not need to repeat per-parameter syntax. This exceeds the baseline of 3 without duplicating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action: 'Update properties of a placed symbol in a KiCAD schematic (.kicad_sch) in-place.' It enumerates concrete capabilities (footprint, value, reference, field labels, custom properties) and clearly differentiates from the sibling tool edit_component by restricting to .kicad_sch files and directing PCB footprint changes to edit_component.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit 'Use this tool to' list covering all major use cases, and an explicit exclusion: 'Operates on .kicad_sch files only — to modify a PCB footprint use edit_component instead.' It also contrasts with delete+re-add, explaining when this tool is preferable because it preserves position and UUID.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Avinash1286/KiCAD-MCP-Server-THEAVI'

If you have feedback or need assistance with the MCP directory API, please join our Discord server