pcb-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PCB_AGENT_DATA | No | Optional path to the data tables directory. Takes precedence over the repository, package, and site data locations. | |
| PCB_AGENT_HOME | No | Directory for locally learned experience data stored in experience.json. | ~/.pcb_agent_mcp/ |
| PCB_AGENT_LEDGER | No | Set to '0' to disable writing the run ledger; otherwise the ledger is enabled. | |
| PCB_AGENT_NGSPICE | No | Optional path to an ngspice binary used by sim_spice when engine is 'ngspice' or 'auto'. | |
| PCB_AGENT_TOOLSET | No | Controls which tools are exposed by tools/list. The default 'core' exposes the 50 entry tools; use 'all' for the full tool set, or a comma-separated list of prefixes such as 'board_,magnetics_'. | core |
| PCB_AGENT_MAX_RESULT_KB | No | Maximum size in KB for a single tool result before it is truncated; set to 0 to disable the limit. | 48 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Calc layer for PCB design. Every numeric answer carries model, basis, precision and assumptions. Some tools refuse to answer unless the governing standard is named or its data table is loaded - do not substitute your own memorised value when that happens. Only the common tools are listed directly: when the capability you need is not in the tool list, call tool_search with the task, then tool_call with the returned name and schema.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calc_capabilitiesD | ... |
| board_summaryD | ... |
| board_componentsD | ... |
| board_netsD | ... |
| board_zonesD | ... |
| board_drcD | ... |
| board_viewD | ... |
| board_rulesD | ... |
| board_fidelityD | ... |
| board_createD | ... |
| board_proposeD | ... |
| board_applyD | ... |
| board_rules_writeD | ... |
| schematic_summaryD | ... |
| schematic_reviewD | ... |
| schematic_proposeD | ... |
| schematic_applyD | ... |
| schematic_pcb_diffD | ... |
| schematic_pcb_syncD | ... |
| epro_inspectD | ... |
| app_detectD | ... |
| app_statusD | ... |
| lceda_pro_statusD | ... |
| lceda_pro_openD | ... |
| lceda_pro_recoverD | ... |
| lceda_pro_verifyD | ... |
| lceda_pro_close_extraD | ... |
| lceda_pro_projectsD | ... |
| unit_convertD | ... |
| width_for_currentD | ... |
| current_capacityD | ... |
| via_resistanceD | ... |
| via_current_allowedD | ... |
| trace_impedanceD | ... |
| width_for_impedanceD | ... |
| diff_impedanceD | ... |
| clearance_requiredD | ... |
| creepage_requiredD | ... |
| lambda_over_20D | ... |
| stackup_designD | ... |
| dfm_checkD | ... |
| decoupling_checkD | ... |
| pdn_impedanceD | ... |
| ir_drop_chainD | ... |
| sim_spiceD | ... |
| thermal_via_arrayD | ... |
| part_searchD | ... |
| part_getD | ... |
| tool_searchD | ... |
| tool_callD | ... |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 50 tools
The tools are largely grouped by domain (board_, schematic_, lceda_pro_) and action, giving agents a reasonable starting point. However, several workflow-step tools like board_propose vs board_apply vs board_create, or board_view vs board_summary vs board_fidelity, have overlapping purposes that could cause misselection without detailed descriptions.
Most tools use snake_case, and domain-prefixed groups (board_, schematic_, lceda_pro_) follow a predictable pattern. Yet the calculation and utility tools mix conventions—verb_noun (unit_convert), noun_noun (current_capacity), and noun_prep_noun (width_for_current)—which breaks a single consistent scheme across the entire set.
With 50 tools, the server is very large and exceeds the comfortable range for an agent to manage effectively. While PCB design is a broad domain, many tools (e.g., eight LCEDA Pro-specific operations, multiple meta-tools) could likely be consolidated or scoped more tightly without losing core functionality.
The surface covers a wide range of PCB design activities: board editing, schematic review, electrical and thermal calculations, DFM checks, simulation, part lookup, and application integration. Minor gaps may exist (e.g., BOM or manufacturing output tools), but the core lifecycle from design to validation appears well-represented.