Skip to main content
Glama
LTspice MCP
by kh6570
README.md
In the name of God, the Most Gracious, the Most Merciful

# LTspice MCP

LTspice MCP is a [Model Context Protocol](https://modelcontextprotocol.io) server for [LTspice](https://www.analog.com/en/resources/design-tools-and-calculators/ltspice-simulator.html). An assistant can edit `.asc` schematics, run the simulator, and read logs and waveforms through stable JSON tools.

The `.asc` file is the source of truth. LTspice produces `.net`, `.log`, and `.raw`. Waveform reads stay inside a 2000-point budget.

The shared server framework is the Python package `mcp-app-core`. `pip install` of this server clones it from GitHub. This repository contains the LTspice editor, command line, and tools.

## Requirements

- Windows
- Python 3.11 or newer
- LTspice XVII (`XVIIx64.exe`) or a later install (`LTspice.exe`)

## Install

```powershell
py -3.12 -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
```

`pip install` clones [mcp-app-core](https://github.com/kh6570/HAbedini-mcp-app-core). Do not clone that repository.

```powershell
.\.venv\Scripts\ltspice-mcp.exe --describe
```

Register the server in Cursor and VS Code. The command does not remove a `qspice` entry from the config.

```powershell
pwsh -ExecutionPolicy Bypass -File .\scripts\setup_mcp.ps1 -WorkspaceRoot "D:\path\to\your\circuit\folder"
```

Then fully restart the IDE. Setup details are in [AGENTS.md](AGENTS.md). Day-to-day use is in the [user guide](docs/user-guide.md).

## Documentation

| Doc | Purpose |
| --- | --- |
| [User guide](docs/user-guide.md) | Install, run, and the limits of the GUI |
| [Tool reference](docs/tool_reference.md) | Every tool, with its required arguments |
| [Architecture](docs/architecture.md) | How a schematic becomes a simulation |
| [Error codes](docs/errors.md) | Stable codes on tool failures |
| [Security](docs/security.md) | What the sandbox does |
| [Changelog](CHANGELOG.md) | The released changes |

## License

MIT

TDQS

C2.4/5.0

Scored across 145 tools

Disambiguation2/5

145 tools include many overlapping run/prepare/measure/export operations (e.g., run_simulation, submit_batch, submit_remote_simulation; prepare_ac vs add_instruction). While names are descriptive, an agent will struggle to choose the right tool for a given task.

Naming Consistency5/5

All tool names use snake_case with a leading verb (add_, get_, list_, prepare_, run_, etc.), forming a consistent verb_noun pattern. No camelCase or mixed conventions.

Tool Count1/5

145 tools is extreme for any MCP server, far exceeding the 50+ threshold for mismatch. Many tools are thin wrappers around specific SPICE directives or analysis types, bloating the surface.

Completeness4/5

The surface covers schematic editing, simulation setup, execution, batch/remote runs, analysis, and export comprehensively. Minor gaps exist, such as no direct schematic deletion or fully supported live GUI control, but core workflows are complete.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues