schematic-mcp-bridge
Enables AI agents to design electrical schematics through a high-level semantic API, handling components, pins, nets, validation/ERC, auto-layout, and SVG/KiCad rendering without requiring coordinate or file internals.
README
schematic-mcp
AI-agent-friendly system for building electrical schematics: an MCP server
exposes a high-level, semantic API (components, pins, nets) so an LLM never
has to touch coordinates, wires, or .kicad_sch internals directly.
AI Agent → MCP / high-level API → semantic schematic model → validation/ERC
→ automatic layout → SVG and/or KiCad schematic
See schematic_mcp_requirements.md for the full spec and SKILL.md
for agent rules.
Status
-
Stage 1 done: minimal semantic model (
Component,Pin,Net,Schematic) with JSON save/load, inschematic/model.py. -
Stage 2 done: KiCad symbol library import backed by SKiDL (
schematic/library.py:search_components/get_component_pins/instantiate) and structural validation + basic ERC (schematic/validation.py:validate/run_erc). Tested against real official KiCad symbol libraries vendored intests/fixtures/kicad-symbols/(Device,MCU_Espressif,Sensor_Current). -
Stage 3 done: naive auto layout (
schematic/layout.py, one row of boxes, no overlap), an SVG renderer (schematic/renderer.py) that draws component boxes with pin numbers/names and net-name labels next to each pin — no drawn wires yet, connectivity is shown via labels (see requirements section 11); and a CLI (cli/main.py:search,validate,render). -
Stage 4 done: MCP server (
mcp_server/server.py) exposing the full section 8 tool list — library lookup, schematic lifecycle, connections, layout hints, validation/ERC, SVG output — over stdio. The stateful logic lives inmcp_server/tools.py::SchematicSession(one active schematic per session), framework-free so it's tested directly without an MCP client.set_placement_hint/set_pin_side/group_componentsstore intent on the model already. -
Stage 5 done:
auto_layoutnow honorsleft_of/right_ofplacement hints (topological reorder of the row; other relations are still ignored, a real 2D layout is stage 7 territory if needed). Newschematic/routing.pydraws an actual orthogonal wire between two components when they land as immediate neighbors and it's a 2-endpoint net with pins facing each other — otherwise still a net label, since routing around an intervening box is real routing-algorithm work (deferred).set_pin_side/group_componentsare still stored-but-unconsumed. -
Stage 6 done:
.kicad_schexport (schematic/exporters/kicad.py), reusing SKiDL's own schematic generator rather than hand-rolling a KiCad file writer — it already draws real classical symbols with correct geometry (section 4/19's stated preference). Only works for components sourced from a real library symbol viaadd_component; raisesKicadExportErroron a hand-authored/invented component or one that doesn't resolve, rather than silently producing a broken file.examples/esp32_ina226.jsoncan't export (its ESP32/INA226 pins are hand-authored placeholders, not real symbols) — seeexamples/build_rc_filter.pyfor a small schematic built entirely from real library parts that does. Needed vendoringpower.kicad_symtoo (SKiDL's schematic generator loads it unconditionally).Also fixed a real bug found while building that RC filter example:
ComponentLibrary.instantiate()defaultedreferenceto the bare library ref_prefix ('R' for every resistor) instead ofcomponent_id— so adding a second resistor without an explicitreference=produced a falseduplicate_referenceERC error on a perfectly valid schematic.
MVP is now complete end-to-end (search → add → connect → validate/ERC → SVG / KiCad export) via both the CLI and the MCP server. What's left is optional polish: stage 7 (ELK-based 2D layout + general wire routing) is explicitly "only if this isn't good enough" territory in the spec, not committed to.
Development
python3 -m pip install --user --break-system-packages -e ".[dev]"
PYTHONPATH=. python3 -m pytest
# CLI
PYTHONPATH=. python3 -m cli.main search resistor
PYTHONPATH=. python3 -m cli.main validate examples/esp32_ina226.json
PYTHONPATH=. python3 -m cli.main render examples/esp32_ina226.json -o out.svg
PYTHONPATH=. python3 -m cli.main export-kicad examples/rc_filter.json -o out.kicad_sch
# MCP server (stdio)
PYTHONPATH=. python3 -m mcp_server.server
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.