Zaptrace

MCP开发工具

提供方 oaslananka

开发工具 未标注 会话登录 社区 / 第三方 CursorCodexZed
查看接入方式

AI-native, verification-first EDA kernel for prompt-to-fab electronics: ERC/DRC, routing, KiCad/Gerber export, MCP server, SDK, proof packs.

一句话选型结论

按资料字段整理

Zaptrace 属于开发工具类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Cursor、Codex、Zed,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

支持客户端

安装与配置

未标注 会话登录
上游未给出传输方式
zaptrace-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zaptrace当前 未标注 未标注 未标注 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方oaslananka上游标注的维护方 oaslananka
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · python本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

19.5 KB
来自项目仓库与上游目录的原文,未做删改

⚡ ZapTrace

AI-native, verification-first EDA kernel for prompt-to-fab electronics.

Prompt-to-Fab, with proofs.

Intent → normalized design → schematic → ERC → placement → routing → DRC → BOM → manufacturing package → auditable proof pack.

Documentation ·
Quickstart ·
Validation Environment ·
Roadmap ·
Governance ·
Security ·
Safety

> [!WARNING]
> Pre-1.0. ZapTrace is a verification-first EDA kernel, not a fabrication guarantee. All generated outputs require human engineering review before fabrication or use. See Safety Disclaimer.

> [!NOTE]
> Proof Pack = evidence layer, not absolute correctness. Proof packs record configured checks, artifacts, assumptions, and pass/fail evidence. A clean proof pack does not mean a board is manufacturer-approved, production-ready, or safe to fabricate without review.


What ZapTrace Is

  • A Python SDK for programmatic electronics design — parse, validate, place, route, export.
  • A CLI (zaptrace) for quick design iteration from the terminal.
  • An MCP server (zaptrace-mcp) whose default expert surface exposes 93 design tools plus 3 session-administration tools, with smaller task-oriented inspect, design, verify, repair, and release surfaces for bounded workflows.
  • A REST API for web-based design workflows.
  • A verification engine — Electrical Rule Checking (ERC) + Design Rule Checking (DRC) baked in.
  • A manufacturing export pipeline — Gerber RS-274X, Excellon drill, BOM, pick-and-place, KiCad.
  • A proof-pack generator — auditable, reproducible artifact bundles for every design.

What ZapTrace Is Not

  • ❌ Not a replacement for KiCad, Altium, or Eagle — ZapTrace is a backend engine, not a full PCB editor GUI.
  • ❌ Not a general-purpose SPICE simulator or solver-grade sign-off tool — ZapTrace can export SPICE and run bounded ngspice-backed evidence gates, but these do not replace full analog verification or qualified engineering review.
  • ❌ Not a replacement for human engineering judgment — all outputs require review before fabrication.
  • ❌ Not fabrication-proven — ZapTrace is pre-1.0. Manufacturing outputs are experimental.
  • ❌ Not fabrication-ready or production-ready — no claim of fitness for manufacturing is made.
  • ❌ Proof Pack is not a correctness guarantee — it is an evidence layer that records what was checked and what passed/failed. Absence of errors does not mean the design is correct or manufacturable.
  • ❌ KiCad Oracle (ERC/DRC) is external validation, not absolute correctness — it catches rule violations the rules know about. A passing KiCad Oracle check does not guarantee a working circuit.
  • ❌ Fab profiles are not manufacturer approvals — built-in profiles match common manufacturer capabilities, but you must verify against your specific manufacturer's current specifications. Always obtain pre-fabrication approval.
  • ❌ GitHub hardware CI cannot catch all hardware errors — CI runs on simulated or limited hardware; physical validation (probe, power-up, functional test) is irreplaceable.

Status

Area Status
Design parsing ✅ Implemented
Schematic synthesis ⚠️ Template selection (keyword-matches a pre-built template; not from-scratch synthesis)
ERC (Electrical Rule Checking) ✅ Implemented
Component placement ✅ Implemented
Grid-based routing ✅ Implemented
Net-aware smart routing ✅ Implemented
DRC (Design Rule Checking) ✅ Implemented
Net classification (EE knowledge) ✅ Implemented
Copper pour generation ✅ Implemented
Gerber RS-274X export ✅ Implemented
Excellon drill export ✅ Implemented
BOM (CSV + JSON) export ✅ Implemented
Pick-and-place export ✅ Implemented
KiCad schematic export ✅ Implemented
KiCad hierarchical project import ✅ Implemented
EasyEDA Standard import/export (round-trip ≥0.75) ✅ Implemented (single flat JSON; import-only, no PCB editor)
EasyEDA Pro writer (import-only via KiCad) ✅ Implemented (ZIP+JSONL; distinct from Standard)
Altium ASCII schematic import ✅ Implemented (ASCII export only; OLE binary not supported)
SVG schematic rendering ✅ Implemented
Manufacturing ZIP bundle ✅ Implemented
MCP server (96 exposed tools: 93 design + 3 session administration) ✅ Implemented
Power-tree architecture planner + netlist emit ✅ Implemented
REST API server ✅ Implemented
Design diff ✅ Implemented
Full pipeline (autopilot) ✅ Implemented
Proof-pack system ✅ Implemented — evidence/sign-off foundation; not a correctness guarantee
Plugin system 🚧 Experimental — signed runtime policy documented; production sandboxing still required
Review Studio ✅ Implemented — human-review panels, proof-pack evidence, benchmark readiness
SPICE netlist export ✅ Implemented foundation — DC gate is evidence/skip aware, not full analog sign-off
DFM (Design for Manufacturing) ✅ Implemented foundation — fab profiles, manufacturing evidence, current/thermal/SI risk reports
Multi-board design 🔮 Planned — post-0.3.0
RF/microwave awareness 🔮 Planned

v0.3.0 Release Scope

ZapTrace 0.3.0 is an evidence-hardening release. It adds bounded autonomous sign-off vocabulary, requirements coverage, assumption evidence, KiCad oracle evidence, manufacturing/DFM evidence, component/datasheet/footprint provenance, layout/power/SI/PI risk reports, known-failure benchmark mutation coverage, and Review Studio benchmark readiness panels.

This release still makes no fabrication-readiness claim. A pass means the configured evidence gates did not block; it does not mean the design is manufacturer-approved, production-ready, or safe to fabricate without human engineering review.


Quickstart

ZapTrace is pre-1.0. The registry distribution identity is zaptrace-eda while the Python import package and CLI remain zaptrace. v0.3.5 is available on PyPI; its immutable tagged workflow failed the container-security gate before GitHub Release creation, so the tag is retained as partial-release evidence rather than rewritten. Active development has advanced to 0.3.6.dev0. For a clean PyPI install of the latest published package:```bash
uv venv --python 3.13
uv pip install "zaptrace-eda==0.3.5"
source .venv/bin/activate

Run diagnostics

zaptrace doctor

First run: scaffold a design locally (the published wheel does not

contain the repository's examples/ directory).

zaptrace init sensor-demo --template esp32_i2c_sensor
zaptrace parse sensor-demo/design.yaml
zaptrace view sensor-demo/design.yaml --output sensor-demo/review

Create KiCad/inspection outputs inside the working directory.

Generation success does not mean ERC/DRC or fabrication readiness.

zaptrace pipeline --source sensor-demo/design.yaml --output sensor-demo/build


---

## CLI Usage```bash
# Parse a design YAML
zaptrace parse design.yaml

# Inspect a parsed design
zaptrace inspect my_design

# Run ERC validation
zaptrace erc my_design

# List ERC rules
zaptrace erc-rules

# Place components
zaptrace place my_design

# Route nets
zaptrace route my_design

# Generate BOM
zaptrace bom my_design
zaptrace bom my_design --format json

# Generate design report
zaptrace report my_design --output report.md

# Render schematic SVG
zaptrace svg my_design --output schematic.svg

# Export to KiCad
zaptrace kicad my_design output/kicad/

# Diff two designs
zaptrace diff design_a design_b

# Search library
zaptrace library search resistor
zaptrace library get 0402_10k

# Run full pipeline
zaptrace pipeline --source design.yaml --output build/
zaptrace pipeline --intent "ESP32 I2C sensor node"

Python SDK Usage```python

from zaptrace.core.parser import parse_file
from zaptrace.erc.runner import ERCRunner
from zaptrace.algo.placer import place_components
from zaptrace.algo.router import route_design_smart
from zaptrace.export.manufacturing import generate_manufacturing_bundle
from zaptrace.ee.classifier import classify_design

Parse

design = parse_file("design.yaml")

Validate

runner = ERCRunner()
erc_result = runner.run(design)

Classify nets

classify_design(design)

Place & route

positions = place_components(design)
routing, route_result = route_design_smart(design, positions)

Export

bundle = generate_manufacturing_bundle(design, "build/")
print(f"Gerber layers: {list(bundle['gerber_layers'].keys())}")


---

## MCP Usage

ZapTrace exposes an MCP server for AI agent integration.```bash
# Start MCP server (stdio mode)
zaptrace-mcp

# Start MCP server (HTTP loopback mode)
zaptrace-mcp-http

Configure in your AI client's MCP settings:```json
{
"mcpServers": {
"zaptrace": {
"command": "zaptrace-mcp"
}
}
}


See MCP quickstart for the tool catalog and agent plugin publication for product-owned skills, runtime boundaries, and activation gates.

---

## REST API Usage```bash
# Start the secure loopback server on 127.0.0.1:8080.
zaptrace-api

# Health does not require a bearer token.
curl http://127.0.0.1:8080/health

For the authenticated REST and MCP HTTP Compose deployment, copy .env.example, set both token values, and run docker compose up --build --wait. See REST API production hardening and MCP HTTP deployment.


Manufacturing Export

ZapTrace generates all files needed for PCB fabrication:

Artifact Format Status
Copper layers Gerber RS-274X ✅
Drill file Excellon ✅
Bill of Materials CSV / JSON ✅
Pick-and-place CSV ✅
Manufacturing bundle ZIP ✅
KiCad project .kicad_pcb, .kicad_sch ✅
Schematic SVG ✅
Design report Markdown ✅
# Generate everything
zaptrace export manufacturing my_design --output build/board

Proof Pack

A Proof Pack is an auditable, reproducible artifact bundle that explains what ZapTrace generated and why.```bash
zaptrace proof-pack design.yaml --output build/proof-pack


Each proof pack contains:
- Design inputs and normalized model
- ERC results (what was checked and what passed/failed)
- DRC results
- BOM and supply-chain overview
- All manufacturing artifacts
- Decision log
- Reproducibility metadata
- Warnings and review checklist

See docs/strategy/proof-pack-spec.md for details.

---

## Verification Model

ZapTrace uses a layered verification model. Each layer produces evidence; none is a correctness guarantee.

### Evidence Layers

| Layer | What It Does | What It Does NOT Do |
|-------|-------------|---------------------|
| **Parser** | Validates design YAML structure and constraints | Does not verify circuit functionality |
| **ERC (29 rules)** | Checks electrical rules (net connectivity, pin compatibility, power, power-tree, DNP-aware) | Does not simulate the circuit or verify timing |
| **DRC (16 rules)** | Checks physical design rules (clearance, width, drill) | Does not guarantee manufacturability |
| **KiCad Oracle** | Exports to KiCad and runs KiCad's ERC/DRC as external validation | KiCad may have different rules; a pass does not mean the design is correct |
| **Proof Pack** | Records all verification results, artifact hashes, environment metadata, and decisions | Evidence of what was checked, not a guarantee of correctness |
| **Fab Profiles** | Documents manufacturer capabilities (min trace, min drill, layers) | Not a manufacturer approval; always verify with your fab house |
| **GitHub Hardware CI** | Runs hardware-level integration checks on available runners | Cannot reproduce all real-world hardware conditions; physical testing required |

### What "Verification-First" Means

- Verification is **built into the pipeline**, not bolted on after export.
- Every design artifact has an auditable chain: who checked what, with which tool, and what result.
- The design pipeline stops on hard errors (ERC/DRC failures) and requires explicit override.
- **Human engineering review is mandatory** before fabrication. No automated tool can replace domain expertise.

### Non-Claims

ZapTrace does **not** claim:

- **Fabrication-ready** — no automated verification pipeline can guarantee a board will fabricate correctly.
- **Production-ready** — pre-1.0; APIs and outputs may change.
- **Manufacturer-approved** — fab profiles are reference configurations, not approvals.
- **Guaranteed correctness** — all verification tools have blind spots.
- **Fully automatic manufacturing** — every manufacturing output requires human review and fab house approval.

---

## Architecture```mermaid
graph TD
    A[YAML Design File] --> B[Parser]
    A1[Natural Language Intent] --> B1[Synthesis Engine]
    B1 --> B

    B --> C[Design Model<br/>Pydantic]
    C --> D[EE Knowledge<br/>Classifier]

    D --> E[ERC Engine]
    E --> F{RC Passed?}

    F -->|Yes| G[Placer]
    F -->|No| H[Suggest Patches]
    H --> C

    G --> I[Router]
    I --> J[DRC Engine]

    J --> K{DRC Passed?}
    K -->|Yes| L[Export Pipeline]
    K -->|No| I

    L --> M[Gerber]
    L --> N[Excellon]
    L --> O[BOM]
    L --> P[Pick-and-Place]
    L --> Q[KiCad]
    L --> R[SVG Schematic]

    L --> S[Proof Pack Generator]
    S --> T[manifest.json + artifacts]

    C --> U[MCP Server]
    C --> V[REST API]
    C --> W[CLI]

Example Gallery

Example Description
ESP32 I2C Sensor Node ESP32-C3 reading temperature/humidity over I2C
RP2040 USB HID RP2040-based USB keyboard controller
USB-C LiPo Charger USB-C powered LiPo charger with protection
STM32 RS485 Node Industrial STM32 RS485 Modbus node
nRF52840 BLE Sensor BLE environmental sensor with nRF52840

See examples/ for design YAML files and walkthroughs.


Safety Disclaimer

> ⚠️ ELECTRONICS DESIGN IS INHERENTLY RISKY.
>
> ZapTrace is pre-1.0 software. All outputs — schematics, layouts, manufacturing files — must be reviewed by a qualified electrical engineer before fabrication or use.
>
> Incorrect PCB designs can cause:
> - Fire or thermal damage
> - Equipment damage
> - Electrical shock
> - Radio interference (legal liability)
> - Complete system failure
>
> ZapTrace is provided as-is, without warranty of any kind. The maintainers assume no liability for damages arising from the use of this software or its outputs.
>
> Verification tools are evidence layers, not correctness guarantees.
> - A passing ERC/DRC/KiCad Oracle check does not mean the design is correct or manufacturable.
> - A valid Proof Pack attests what was checked, not that the design is safe.
> - GitHub hardware CI cannot replace physical testing.
> - Fab profiles are reference configurations, not manufacturer approvals.
>
> If you are not an electrical engineer, consult one before fabricating any ZapTrace-generated design.
>
> See docs/SAFETY.md for the full safety policy.


Persistent local state

Controlled deployments can persist committed designs, immutable version lineage, snapshots, transactions, audit events, object ACLs, and evidence identities in local SQLite:bash export ZAPTRACE_SESSION_STORE_ROOT="$HOME/.local/share/zaptrace/state" zaptrace-mcp

Persistence is opt-in; unset deployments retain process-local behavior. Isolated workers cannot write durable state directly, active proof/release references protect artifacts from retention cleanup, and startup fails closed on schema or integrity errors. See Persistent versioned state for backup, restore, migration, deployment modes, and non-claims.


Roadmap

Horizon Focus
Legacy baseline (v0.3.3) PyPI-only release without public Git provenance; preserved as immutable historical evidence
Failed candidate (v0.3.4) Aborted release candidate at commit 76ecc97; workflow failed before publication and is preserved immutably as failed evidence
Partial release (v0.3.5) PyPI artifacts published and verified; container-security gate failed before GitHub Release creation, so the immutable tag is retained as partial-release evidence
Active development (0.3.6.dev0) Post-release development line; future publication must pass container security before TestPyPI/PyPI promotion
Next (v0.4.0) Topology and layout depth, bounded evaluation coverage, review evidence, and controlled release-readiness hardening
Later Larger component library, live distributor integrations, deeper routing fidelity, solver-grade SI/PI/thermal integrations, multi-board workflows

See docs/ROADMAP.md for the full roadmap.


Contributing

We welcome contributions! See CONTRIBUTING.md for guidelines.

  • Issue tracker: GitHub Issues
  • Questions and design discussion: use GitHub Discussions; use Issues for confirmed bugs and scoped work
  • Code of Conduct: CODE_OF_CONDUCT.md

License

Current project-authored ZapTrace source code is available under the PolyForm Noncommercial License 1.0.0. Commercial use requires a separate written license from the copyright holder; see COMMERCIAL-LICENSING.md and LICENSING.md.

Earlier versions and revisions already released under MIT remain available under the MIT terms that applied when they were published. Third-party material keeps its own license terms.


Current Limitations

  • Pre-1.0: APIs are unstable and may change without notice.
  • No interactive PCB GUI: Primary surfaces are CLI, SDK, MCP, REST, generated artifacts, and Review Studio evidence views.
  • No fabrication approval: No claim of manufacturing readiness is made; all outputs require qualified human engineering review.
  • Heuristic analysis: Current thermal, SI/PI, impedance, current-density, and power reports are evidence pre-checks, not solver-grade sign-off.
  • Algorithmic routing: Routing is grid/net-aware, but not a professional push-and-shove interactive router.
  • Bounded synthesis: Synthesis is block/template/requirements driven, not open-ended from-scratch invention for arbitrary circuits.
  • Limited package/library breadth: Many module, DFN/LGA/aQFN/RJ45/RF land patterns still require datasheet-backed geometry expansion.
  • KiCad Oracle is external validation: KiCad's own ERC/DRC has limitations. A passing check does not guarantee circuit functionality.
  • Fab profiles are not manufacturer approval: Always verify against your specific fab house and current manufacturer capabilities.
  • Benchmark pass is regression evidence: It does not imply fabrication safety or production readiness.
  • GitHub hardware CI ≠ physical testing: CI cannot reproduce all real-world failure modes.
  • KiCad export is primarily outbound: Import/round-trip fidelity is still a future hardening area.
  • Plugin system is experimental: Signed-runtime policy exists, but production sandboxing requires further hardening.

Repository Maturity and Community Health

ZapTrace is managed as a pre-1.0 professional source-available project. The repository keeps its maturity evidence, governance, contribution expectations, release process, and security posture public so users and contributors can review the project's operating model.

  • Repository maturity report
  • OpenSSF evidence
  • OpenSSF gap analysis
  • Governance
  • Maintainers and access continuity
  • Support policy
  • Development standards
  • Testing policy
  • Release process
  • Dependency management
  • Release integrity verification

Current maturity target: professional source-available engineering maturity. Earlier OpenSSF/FLOSS evidence describes the MIT-licensed period and should not be read as a current FLOSS-license claim; governance limitations such as solo maintenance also remain explicit.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Zaptrace 怎么安装?

在客户端按下面的安装命令接入:zaptrace-mcp。装完在客户端配置里引用同一个包或端点。

Zaptrace 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Zaptrace 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zaptrace 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Zaptrace 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Zaptrace 需要什么运行环境?

运行时为 python。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。