ltspice-mcp
MCP serverCommunity
Runs LTspice or ngspice, returns named measurements such as phase margin and overshoot, and edits LTspice .asc schematics. By cognitohazard.
68 starsUpdated 1 day agoGitHub data from 5 Nov 2026
At a glance
- Type
- MCP server
- How it connects
- Drives a running copy of the tool
- Access
- Can modify models
- Tool versions
- LTspice (primary; Windows, WSL2, Linux via Wine), ngspice; live editing in an open window needs LTspice 26.1+ on Windows; QSPICE and Xyce for netlists
- Operating systems
- Windows, macOS, Linux
- Needs a LTspice licence
- No
- Transport
- Local (stdio)
- AI clients documented
- Claude Code, Claude Desktop, Cursor, Windsurf, Gemini CLI, Continue, Cline, Zed
- Licence
- GPL-3.0
- Language
- Python
What it can do
- Eight tools run circuits, sweeps and Monte Carlo sets as background jobs and read the binary .raw output themselves.
- Returns time- and frequency-domain measurements by name (rise time, settling, THD, cutoff, gain and phase margin, Q) plus device operating points such as gm, gds and vth.
- Creates and edits .asc schematics with checks for floating pins, dangling labels and wires that cross pins, and refuses to edit a file that changed since it was read.
- The same engine is importable as a Python API for optimisers, fits and CI checks.
Limitations
- Marked work in progress; 0.6.0 replaced the earlier tool set, so pin 0.5.* if you rely on it.
- Editing .asc schematics needs LTspice, because it uses LTspice's symbol libraries.
- Without a sandbox setting the tools can reach any path, and run_code executes Python with the server's permissions.
Install
/plugin marketplace add cognitohazard/ltspice-mcp
/plugin install ltspice-mcpuv tool install ltspice-mcp{
"mcpServers": {
"spice": { "command": "ltspice-mcp", "args": [] }
}
}MCP servers and skills run code on your computer. Review the source before installing.
AI-generated models, drawings and results must be checked by a qualified engineer before use.