fireostendere/mcp_diptrace

DipTrace MCP is a local Model Context Protocol server for reading, analysing,
reviewing, and performing guarded edits on DipTrace PCB and schematic projects.
It consists of:
- diptrace-mcp, the MCP server used by Codex, Claude Desktop, and other MCP
clients;
- diptrace_mcp_bridge.exe, the Windows plug-in bridge for projects currently
open in DipTrace;
- an internal EDA-intelligence layer for deterministic schematic/PCB intent,
candidate generation, scoring and guarded improvement;
- an optional cinematic presentation layer for calibrated visible DipTrace UI
replay and MP4/GIF capture.
Headless cinematic examples
Schematic assembly
This real DipTrace Schematic capture assembles a two-channel BSS138 I²C level
shifter: all 16 symbols appear one at a time, followed by the six electrical
nets. The recording was produced on an isolated Win32 desktop without taking
over the operator's cursor or keyboard. The editable source is
i2c-level-shifter.dchxml; the full-resolution
recording is i2c-level-shifter-demo.mp4.
PCB layout
The matching 25×12 mm PCB uses compact straight 1×4 2.54 mm headers, symmetric
device placement, 14 routed traces, Top and Bottom GND pours, and 17 distributed
GND stitching vias; connector GND pads request four-spoke thermal reliefs.
Components and routes appear in construction order; GND pours and stitching
appear in the final stage. The
capture is cropped to the complete purple board outline with margin instead of
the editor controls. The editable source is
i2c-level-shifter-pcb.dipxml; the
full-resolution recording is
i2c-level-shifter-pcb-demo.mp4.
The operator confirmed both repository examples in the current DipTrace
configuration on 2026-08-16. This is scoped presentation evidence, not universal
DipTrace compatibility, authoritative refill geometry, or engineering sign-off.
The PCB media was regenerated and visually rechecked after the 17-via update on
2026-08-20; renewed operator confirmation remains pending.
Current status
Version 0.4.0 is the current published unsigned development release. The
immutable GitHub release is v0.4.0, and the matching Python package is
diptrace-mcp==0.4.0 on PyPI.
The published release keeps the public MCP contract frozen at 170 tools and
contains the A1-A8 roadmap closure plus tested cross-platform host paths:
- Windows split per-user/admin installers and portable bundle;
- Ubuntu 24.04 x86-64 one-command deployment with Wine and private-Xvfb GUI
isolation;
- macOS 15 one-command deployment on Apple Silicon and Intel using the official
DipTrace.app bundled Wine runtime and hidden-Win32-desktop automation.
Published v0.4.0 GitHub assets are:
- DipTrace-MCP-Setup-0.4.0.exe;
- DipTrace-MCP-Plugin-Setup-0.4.0.exe;
- DipTrace-MCP-Portable-0.4.0.zip;
- SHA256SUMS.txt.
The v0.4.0 MCPB/registry preparation gate passed before release, but no v0.4.0
MCPB was attached to the public GitHub release. Do not infer an unpublished
bundle from preparation-only CI evidence; the older published MCPB identity
remains a separate historical distribution line.
The Windows executables are unsigned. CI, SHA-256, PyPI Trusted Publishing and
package attestations establish tested behaviour, byte identity and publication
provenance. They do not create a trusted Authenticode signature, universal
compatibility, independent review or production readiness.
main may contain post-release hardening that is not part of immutable
v0.4.0; use the tag when reproducibility matters.
Public Release Status
The project uses the OSI-approved Apache-2.0 open-source LICENSE. Participation
and release controls are documented in CONTRIBUTING.md, GOVERNANCE.md,
docs/LICENSE_DECISION.md, docs/PUBLIC_RELEASE_CHECKLIST.md,
docs/RELEASE_PROCESS.md, CHANGELOG.md, and CITATION.cff. Security reports
use the private security channel; a verified Code of Conduct enforcement channel
is not yet published.
- Python archives are built from an exact allowlist and audited for entry
points, packaged skills, bounds, metadata, and every RECORD hash and size.
- PyPI publication uses GitHub OpenID Connect and a protected pypi
environment; no long-lived PyPI API token is stored.
- The PyPI publish job receives only the already validated wheel and source distribution