ltspice-mcp
MCP server for automating LTspice on macOS, enabling simulation, schematic generation, data extraction, verification, and rendering via natural language or agents.
README
LTspice MCP for macOS
Model Context Protocol (MCP) server that lets agents and MCP clients control LTspice on macOS for simulation, schematic generation, data extraction, verification, and rendering.
This project is designed for practical automation: reliable runs, reproducible artifacts, and outputs that match LTspice behavior closely.
Inspired by:
What You Can Do
- Run LTspice simulations from MCP (
simulateNetlistFile,runSimulation, queue tools). - Generate and refine schematics (
createSchematic*, lint/clean/debug tools). - Render real LTspice images for schematics, plots, and symbols.
- Query RAW vectors and analysis metrics (bandwidth, margins, rise/fall, settling).
- Automate
.measand assertion-driven verification workflows. - Run stepped and Monte Carlo studies with structured results.
Quick Start (5 Minutes)
1) Prerequisites
- macOS with LTspice installed (
/Applications/LTspice.appexpected by default). - Python 3.11+.
uv(recommended) orpip.
2) Install
uv sync
If you prefer pip:
python3 -m venv .venv
source .venv/bin/activate
pip install -e .
3) Start the MCP daemon
./scripts/ltspice_mcp_daemon.sh start
./scripts/ltspice_mcp_daemon.sh status
Default endpoint:
http://127.0.0.1:8765/mcp
4) Grant macOS permissions once
Required for screenshot/render and some UI automation features.
./scripts/ltspice_mcp_daemon.sh trigger-initial-permissions
./scripts/ltspice_mcp_daemon.sh check-accessibility
5) Run a smoke test
uv run python smoke_test_mcp.py \
--transport streamable-http \
--server-url http://127.0.0.1:8765/mcp
Client Configuration
URL-capable MCP clients
[mcp_servers.ltspice]
url = "http://127.0.0.1:8765/mcp"
enabled = true
Claude Desktop via mcp-remote
{
"mcpServers": {
"ltspice-mcp": {
"command": "/opt/homebrew/bin/npx",
"args": ["-y", "mcp-remote", "http://127.0.0.1:8765/mcp"]
}
}
}
stdio (subprocess) mode
{
"mcpServers": {
"ltspice-mcp": {
"command": "ltspice-mcp",
"args": ["--transport", "stdio"],
"cwd": "/absolute/path/to/ltspice-mcp"
}
}
}
Core Capabilities by Category
Setup and diagnostics
getLtspiceStatus,getLtspiceUiStatusdaemonDoctor,tailDaemonLog,getRecentErrors,getCaptureHealth
Simulation and queueing
simulateNetlist,simulateNetlistFile,runSimulationqueueSimulationJob,listJobs,jobStatus,cancelJob,listJobHistory
Schematic workflows
createSchematic,createSchematicFromNetlist,createSchematicFromTemplatevalidateSchematic,lintSchematic,autoDebugSchematicinspectSchematicVisualQuality,autoCleanSchematicLayout
Data, measurements, and verification
getPlotNames,getVectorsInfo,getVectorData,getLocalExtremagetBandwidth,getGainPhaseMargin,getRiseFallTime,getSettlingTimeparseMeasResults,runMeasAutomation,runVerificationPlan,runSweepStudy
Native LTspice rendering
renderLtspiceSchematicImagerenderLtspicePlotImage,renderLtspicePlotPresetImagerenderLtspiceSymbolImagestartLtspiceRenderSession,endLtspiceRenderSession
Reliability Notes
- Streamable HTTP defaults are tuned for compatibility:
json_response = truestateless_http = true
- UI integration is disabled by default (
LTSPICE_MCP_UI_ENABLED=0). - Schematic single-window updates are enabled by default.
- Rendering uses LTspice + ScreenCaptureKit direct-window capture.
- Run artifacts are stored per run to keep historical results stable.
Daemon Operations
./scripts/ltspice_mcp_daemon.sh start
./scripts/ltspice_mcp_daemon.sh restart
./scripts/ltspice_mcp_daemon.sh stop
./scripts/ltspice_mcp_daemon.sh status
./scripts/ltspice_mcp_daemon.sh logs --lines 200
./scripts/ltspice_mcp_daemon.sh logs --follow
Permission helpers:
./scripts/ltspice_mcp_daemon.sh trigger-screen-recording-permission
./scripts/ltspice_mcp_daemon.sh trigger-accessibility-permission
Testing
Run core tests:
PYTHONPATH=src .venv/bin/python -m unittest discover -s tests -v
Run real ScreenCaptureKit integration tests (opt-in):
LTSPICE_MCP_RUN_REAL_SCK=1 PYTHONPATH=src .venv/bin/python -m unittest tests.test_screencapturekit_integration -v
LTSPICE_MCP_RUN_REAL_SCK=1 PYTHONPATH=src .venv/bin/python -m unittest tests.test_plot_render_mcp_real -v
Contributing
Contributions are welcome. Start with:
- CONTRIBUTING.md
- AGENT_README.md for agent-specific workflows
When filing bugs, include:
- MCP server version,
- LTspice version,
- transport mode,
- exact tool call + parameters,
- daemon log excerpts.
Documentation Map
- docs/README.md
- AGENT_README.md
- CHANGELOG.md
- COMPATIBILITY.md
- CONTRIBUTING.md
- SUPPORT.md
- CODE_OF_CONDUCT.md
- SECURITY.md
- MCP resource:
docs://agent-readme - MCP tool:
readAgentGuide
Important Environment Variables
Core:
LTSPICE_BINARYLTSPICE_MCP_WORKDIRLTSPICE_MCP_TIMEOUTLTSPICE_MCP_TRANSPORTLTSPICE_MCP_HOSTLTSPICE_MCP_PORTLTSPICE_MCP_STREAMABLE_HTTP_PATHLTSPICE_MCP_JSON_RESPONSELTSPICE_MCP_STATELESS_HTTP
UI/render:
LTSPICE_MCP_UI_ENABLEDLTSPICE_MCP_SCHEMATIC_SINGLE_WINDOWLTSPICE_MCP_SCHEMATIC_LIVE_PATHLTSPICE_MCP_SCK_HELPER_DIRLTSPICE_MCP_SCK_HELPER_PATHLTSPICE_MCP_VERIFY_WINDOW_CLOSE
Logging:
LTSPICE_MCP_LOG_LEVELLTSPICE_MCP_TOOL_LOGGINGLTSPICE_MCP_TOOL_LOG_MAX_ITEMSLTSPICE_MCP_TOOL_LOG_MAX_CHARSLTSPICE_MCP_DISABLE_UVICORN_NOISE_FILTERSLTSPICE_MCP_DAEMON_LOG_DIR
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.