ngspice-mcp

What is ngspice-mcp?

A Model Context Protocol (MCP) server that provides access to ngspice circuit simulation functionality through a standardized protocol interface. It enables AI language models to interact with ngspice in a controlled and structured way.

How to use ngspice-mcp?

Build using dub build --config=server and run ./ngspice-mcp [options]. The server exposes tools for loading netlists, running simulations (e.g., op, dc, ac, tran), and retrieving vector data with multiple representation formats. The default working directory is the current directory; use --working-dir to change it.

Key features of ngspice-mcp

• Integration with ngspice’s shared library interface
• Standardized MCP protocol implementation
• Synchronous operation with structured data access
• Comprehensive output capture and redirection
• Vector data handling with multiple representation formats
• Support for both server and library usage modes

Use cases of ngspice-mcp

• Load and simulate circuit netlists (DC, AC, transient)
• Retrieve simulation results (vector data) in magnitude‑phase or rectangular form
• Access ngspice output streams (stdout, stderr) as MCP resources
• Programmatically control ngspice from AI language models

FAQ from ngspice-mcp

What is ngspice?

ngspice is a mixed‑level/mixed‑signal circuit simulator. This server wraps its shared library via the MCP protocol.

What are the requirements to run ngspice-mcp?

You need a D compiler (DMD/LDC), the ngspice shared library, the MCP server library (d‑mcp‑server), and the D build system (dub).

How are circuit files and results stored?

Circuit netlists are loaded as text (string or file). Simulation results (vector data) are returned as structured MCP tool responses; model parameters can be stored in an internal SQLite database.

What transports and authentication does ngspice-mcp support?

The README does not mention specific transports (e.g., stdio/SSE) or authentication methods. It implements the standard MCP protocol.

What are the known limits?

The README does not list explicit limits. The server is designed for synchronous, structured interaction with ngspice and includes comprehensive error handling via output streams.