LTspice MCP servers and AI agent skills

How AI connects to LTspice

An MCP server or skill can only do what LTspice lets programs do. LTspice exposes 3 automation interfaces:

• Batch mode and command-line switches (Command line): LTspice runs a netlist without its window when started with -b, leaving the waveforms in a .raw file and messages and .meas results in a .log file; -netlist converts a schematic to a netlist the same way. Every server here builds on that loop: write or patch the circuit, run the executable headless, then parse the output. The linked page is a community-hosted copy of the LTspice help, written for an older release. Documentation
• spicelib and PyLTSpice (Python) (Python): spicelib is an open-source Python library that edits netlists and .asc schematics, launches LTspice and other simulators, and reads .raw and .log files, including stepped and Monte Carlo runs. It isn't an Analog Devices product, but it is the base layer for ltspice-mcp and spicelib-mcp, so its documentation explains much of what those servers can and can't do. Documentation
• Schematic, netlist and model files (Input files): .asc schematics, .asy symbols, .cir and .net netlists, .lib and .inc model files are all text, so an agent can read and patch them directly. Editing an .asc file safely needs LTspice's symbol library for pin positions, which is why schematic editing tools require a local LTspice install.

What Analog Devices offers

The ltspice-mcp documentation states that LTspice 26.1 and later ship an MCP server of their own that registers as "ltspice" and controls the LTspice window, and another server's guide mentions an "Analog installer entry". Analog Devices' LTspice pages couldn't be loaded during this check, so Tresca hasn't confirmed the release from a vendor source and doesn't list it as official yet.

Checked 4 Nov 2026. Sources: ltspice-mcp usage guide, "Alongside LTspice's own MCP server", HAbedini-ltspice-mcp user guide

What you can do with LTspice and AI

• Bias a transistor stage and read gm, gds and vth by name from the operating point instead of scrolling through the .log file.
• Measure a regulator's step response, overshoot and settling time, or the phase and gain margin of a control loop, and get the numbers back directly.
• Run Monte Carlo tolerance studies and parameter sweeps as background jobs and summarise the spread across runs.
• Build or modify an .asc schematic that you can open and inspect in LTspice, with checks for floating pins and dangling labels.
• Compare simulated AC or transient results with bench measurements while fitting a behavioural model.

Taken from the listings' own documentation. Check each listing for exactly what it supports.

Installing

The listings here document setup for Claude Code, Claude Desktop, Cline, Codex, Codex CLI, Continue, Cursor, Gemini CLI, GitHub Copilot CLI, Google Antigravity, VS Code, Windsurf, Zed and opencode. Install steps, copied from each project's own documentation, are on each listing's page. Most LTspice integrations run on your own computer next to LTspice, so you need LTspice installed and licensed on the same machine unless the listing says otherwise.