schematic-mcp
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 |
|---|---|
| open_schematicC | Open a local KiCad .kicad_sch file and build its canonical circuit graph. |
| schematic_summaryB | Return summary information for the currently loaded schematic. |
| list_componentsB | List schematic components, optionally filtering by reference, value, or library id. |
| get_componentB | Get one component including properties, pins, and resolved net names. |
| get_pinB | Get one component pin and its resolved electrical net. |
| list_netsC | List resolved nets, optionally filtering by net name or connected pin. |
| get_netB | Get a net by exact name, including labels and all connected component pins. |
| trace_signalB | Trace one pin to every other pin on the same resolved electrical net. |
| get_mcu_pinmapC | Return a compact pin-to-net map for an MCU or any multi-pin component. |
| validate_pinmapC | Compare firmware pin expectations with schematic nets.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| current_summary_resource | Machine-readable summary of the current schematic. |
| current_model_resource | Canonical JSON model for the currently loaded schematic. |
TDQS
Scored across 10 tools
Each tool targets a distinct aspect: loading, summary, component listing/detail, pin detail, net listing/detail, signal tracing, pin mapping, and validation. No two tools have overlapping purposes, so an agent can unambiguously select the right one for a task.
Most tools follow a clear verb_noun pattern (open_schematic, list_components, get_component, etc.), but 'schematic_summary' is a noun phrase rather than a verb-led name, representing a minor deviation. Overall the pattern is predictable and readable.
With 10 tools, the set is well-scoped for a schematic analysis server. Each tool serves a distinct and necessary function, and the count is within the ideal range for a focused MCP server.
The tool surface covers the full read-only workflow: opening a schematic, obtaining summary info, querying components, pins, nets, tracing signal paths, generating pin maps, and validating against firmware expectations. No critical missing operations for the apparent domain.