SPICE simulation → oscilloscope → verification with Claude Code
Details
- External ID
- 47801255
- Source
- HN
- Company
- —
- Product
- SPICE simulation → oscilloscope → verification with Claude Code
- Website domain
- lucasgerads.com
- Launched
- April 17, 2026
- Cohort
- —
- Upvotes
- 121
- Upvotes percentile
- 0.9125964010282777
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
I built MCP servers for my oscilloscope and SPICE simulator so Claude Code can close the loop between simulation and real hardware.
Enrichment
- Theme
- Model Context Protocol developer tools
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- AI feature
- Project type
- Hobby / open-source project
- Normalized one-liner
- spice circuit simulation and verification
- Manually corrected
- False
Could you build this?
Partial Creating standard Model Context Protocol (MCP) server wrappers is easy, but integrating physical hardware lab instrumentation (LeCroy oscilloscopes) and electrical simulation requires specialized electronics domain knowledge.
What it would actually take: The solution combines Python-based MCP servers using PyVISA/SCPI commands over USB/Ethernet to control test equipment, alongside wrappers around SPICE engines (like ngspice or PySpice). The difficult parts include automated signal processing (synchronizing physical oscilloscope traces with simulated time-domain waveforms) and hardware-in-the-loop validation logic. This requires domain expertise in analog electronics, hardware instrumentation protocols (VISA/SCPI), and signal processing.
Discussion
20 comments analyzed.
Competitors mentioned: FPAA (Field-Programmable Analog Arrays), Gemini, Local LLMs
Concerns raised: Claude Desktop has hardcoded 60-second tool call timeout with no config option, LLMs hallucinate without external verification/ground truth, LLMs lack understanding of circuit physics and topology, Claude getting more expensive and worse quality recently, LLMs struggle with long-running tools (e.g., 50-page PDF extraction)
Feature requests: Local LLM integration instead of cloud service, Configurable timeout for long-running tool calls, Better circuit topology understanding (AST-like representation for SPICE), Ability to handle SPICE convergence failures gracefully
Competitors
Other products that read as similar to this one — 121 launches clear the similarity bar, closest 8 shown.
Attention rank: #12 of 122 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 156 days after the earliest competitor.
- Claude Code skill that uses Codex as MCP server for code review · hn · 2026-02-08 · 7 upvotes · similarity 0.50
- Logic Pro MCP · ph · 2026-09-12 · 1 upvotes · similarity 0.50
- MCPSpec · hn · 2026-02-25 · 7 upvotes · similarity 0.46
- Scispot MCP 🧠 Run Claude inside your governed lifescience lab data · yc · 2026-05-26 · 15 upvotes · similarity 0.45
- Run Claude Code sessions on Linear issues via two MCP servers · hn · 2026-04-30 · 5 upvotes · similarity 0.43
- Fermata · ph · 2026-09-30 · 1 upvotes · similarity 0.43
- Persistent memory for Claude Code with self-hosted Qdrant and Ollama · hn · 2026-02-17 · 8 upvotes · similarity 0.42
- lab-instrument-mcps · github · 2026-09-25 · 9 upvotes · similarity 0.42
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.