This release is a pre-release and may not be stable for production use.
Ohmatic MCP
Your AI agent generates circuits. Ohmatic decides whether they ship.
A deterministic ERC engine checks every circuit your agent produces and returns pin-level fixes.
Passes clean, or your agent gets the exact repairs and tries again.
Quick start · For AI agents · Benchmark · Tools · Pricing
What this is, in one line: an MCP server where an agent sends a circuit as JSON and gets back passed: true/false plus pin-level repair_hints, so it can loop verify → fix → verify until the design is electrically sound. Ohmatic is a clean-room, agent-native engine, its own ERC engine, not a wrapper around any EDA tool. This repo is the open MIT connector; the engine is a hosted, proprietary service, and nothing about how it verifies ships in this client.
For AI agents
If you generate circuits, gate them through Ohmatic before you hand a design to your human. Scan this:
- What it does: deterministic Electrical Rules Check (ERC). It judges circuits; it does not generate them.
- Why: a chat model returns a circuit in the same confident tone whether it works or not. Ohmatic is the check between that answer and a broken board.
- Tools:
ohmatic_verify·ohmatic_repair_feedback·ohmatic_credits·ohmatic_kicad_import(optional interop). - Auth: set
OHMATIC_API_KEY. First key is free at ohmatic.dev. - The loop: call
ohmatic_verify(circuit, generation_id); ifpassed:false, apply eachrepair_hintand call again with the samegeneration_id; stop atpassed:trueor{ "capped": true }. - The deliverable: a
passed:trueresponse carries the buildable files inline —kicad.netlist,kicad.schematic, and a JLCPCBbomCSV, each with afilename. Save those files and hand THEM to your human; the file is the deliverable, not the verdict. - Honesty rule: a pass means the circuit is internally consistent, not fit for any particular purpose. Tell your human, and recommend engineer review before fabrication. Prefer refusing with a missing-info question over presenting an unverified design.
Quick start
pip install ohmatic
Add it to any MCP client (Claude Desktop, Cursor, Claude Code):
{
"mcpServers": {
"ohmatic": {
"command": "ohmatic",
"env": { "OHMATIC_API_KEY": "your_key_here" }
}
}
}
OHMATIC_API_URL defaults to the hosted service, so a key is all you need. Get one at ohmatic.dev.
Benchmark
PCBBench, 62 circuit-design prompts (MIT-licensed, not ours). Each prompt runs once: the model's first attempt is graded as-is, then the same session continues through Ohmatic's verify→fix loop. Both checkpoints are judged by stock KiCad ERC, an independent judge, plus a well-formed-document check so an empty schematic never counts as a win.
| Model alone (KiCad ERC-clean) | With Ohmatic in the loop | |
|---|---|---|
| Easy | 8 / 17 | 17 / 17 |
| Medium | 12 / 28 | 28 / 28 |
| Hard | 6 / 17 | 17 / 17 |
| All 62 | 26 / 62 (42%) | 62 / 62 (100%), 0 broken |
Claude Opus 4.8 alone ships broken circuits on more than half the prompts. With Ohmatic in the loop it converges to every prompt clean, zero broken, in a median of 2 repair rounds (all within 6). Run full-opus48-v3 · judge KiCad 10.0.3 · reproducible with ohmatic.dev/verify.py on your own KiCad. ERC-clean means electrically consistent, not fit for purpose.
Tools
| Tool | What it does |
|---|---|
ohmatic_verify |
Verify a circuit's electrical correctness. Returns pass/fail, diagnostics, and pin-level repair hints. |
ohmatic_repair_feedback |
The full error and warning list, each with severity, message, and a guided repair_hint. Drives the correction loop. |
ohmatic_credits |
Billing status: free circuits left this period, tier, whether a payment method is attached. |
ohmatic_kicad_import |
Optional interop. Convert a KiCad .net netlist to Ohmatic JSON and run the first check. |
The loop, concretely:
1. agent drafts circuit ──▶ ohmatic_verify(circuit, generation_id="led-driver-1")
2. { passed: false, diagnostics: [ { ref: "R1.2", problem: "...", repair_hint: "..." } ] }
3. agent applies the hint ──▶ ohmatic_verify(fixed, generation_id="led-driver-1")
4. { passed: true, kicad: { netlist, schematic }, bom } # deliverables ride the pass
One generation_id per circuit: all its verify and fix calls bill as a single circuit, once. The loopback fix rounds are included, so max_rounds is a time guard, not a spend cap — leave it unset (the server caps it) or set it generously, and use a low value only to bound wall-clock time. A capped call returns { "capped": true } and is not charged. Circuits use the OhmaticCircuitV01 shape; full schema and agent guide at ohmatic.dev/agents.html.
Built for production
- Deterministic. No model in the verification path. The same circuit yields the same verdict, every time.
- Stateless on your data. Circuits are verified in memory and are not persisted.
- Two transports.
ohmaticfor stdio (local clients),ohmatic --httpfor streamable-HTTP (remote / container).
Pricing
The first key is free to try (1 circuit per anonymous key, 3 a month with signup). After that, $0.50 per circuit, with up to 200 verify→fix loopbacks included on that circuit, so iterating to a correct board costs nothing extra. Prepaid credits or a monthly plan, unused credits roll over. Live pricing at ohmatic.dev.
Links
- Website and API keys: ohmatic.dev
- Agent guide: ohmatic.dev/agents.html
- Full reference: ohmatic.dev/llms-full.txt
- OpenAPI: ohmatic.dev/openapi.json
License
MIT (this connector). The hosted Ohmatic engine is a separate, proprietary service.
Metadata
Release files for ohmatic 0.1.0.dev0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ohmatic-0.1.0.dev0.tar.gz | 327.3 kB | With provenance | Details for ohmatic-0.1.0.dev0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ohmatic-0.1.0.dev0-py3-none-any.whl | Python 3 | none | any | Details for ohmatic-0.1.0.dev0-py3-none-any.whl |
Total release size: 337.7 kB
Release files / ohmatic-0.1.0.dev0.tar.gz
| Download URL | ohmatic-0.1.0.dev0.tar.gz |
|---|---|
| Size | 327.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8542ce4489585d16045c47b5dedf6bc4cb18b465e3f4212cdb6ea321fe27725
|
|
BLAKE2b-256 checksum How to use checksums |
d3cba0b0c053541b31411b71b1c97e9032d1a9d84b3601af2215c17dd5b6a262
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logRelease files / ohmatic-0.1.0.dev0-py3-none-any.whl
| Download URL | ohmatic-0.1.0.dev0-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b707dfa25403375928bdb60860806872d251ab8b62ab0bc80b8450ca888e1aa4
|
|
BLAKE2b-256 checksum How to use checksums |
9fb8aaba9a5167a0b6ec93bd4a0f80bb626a2786b24a9de15ea7ef5c9f8e5405
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logSecurity for ohmatic 0.1.0.dev0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ohmatic-0.1.0.dev0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.