LV Forge
Provides tools for reviewing LabVIEW VIs, including inspecting saved block diagrams and connector panes, comparing revisions, rendering SVG diagrams, checking runnability through a live LabVIEW IDE, and generating HTML inspection reports.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
LV Forge
LV Forge brings LabVIEW VI review into an MCP client. Use it to trace the wiring in a saved block diagram, compare two revisions of a VI, or ask the LabVIEW IDE whether a VI is runnable.
Capabilities
Tool | Use it to | Source |
| Inspect nodes, wiring, and connector pane terminals. The result includes the saved file's SHA-256 hash. | Saved VI |
| Compare two saved VIs for changes in diagram structure and dataflow. | Two saved VIs |
| Generate a temporary SVG of a block diagram. | Saved VI |
| Read the execution state and runnability reported by the IDE. | Live LabVIEW IDE |
| Generate a self-contained HTML inspection report with the VI hash, saved version, diagram, and diagnostics. | Saved VI, with an optional live IDE check |
The offline tools use LVKit and can work without a running IDE. The live check uses Windows ActiveX and has been verified with LabVIEW 2020 32-bit. It may load the VI into the IDE. It never executes or saves the VI. Exact broken-wire counts and unsaved-edit status are reported as unknown.
Offline results include warnings, notices, and a partial_analysis flag. LV Forge uses a fresh temporary LVKit cache for each call so cached results do not suppress parser warnings. It preserves usable partial output and surfaces warnings even when LVKit exits successfully. Inspect the warnings before relying on a diagram or diff. The lv_diff result contains its text in the diff field.
Related MCP server: EPLAN MCP Server
Install
Use Python 3.11 or newer. Run these commands in PowerShell:
git clone https://github.com/harisunder1991/lv-forge.git
cd lv-forge
py -3.11 -m venv .venv
.\.venv\Scripts\python.exe -m pip install -r requirements.txtTry the bundled examples
Run this from the repository root:
.\.venv\Scripts\python.exe examples\quickstart.pyThe demo inspects the array-sum VI, compares it with the array-product VI, and prints the path to an SVG. It runs offline by default. To try the live check, start LabVIEW and add --live. See the example guide for the opt-in COM activation option and expected results.
Connect your MCP client
For clients that accept an mcpServers JSON configuration, replace C:/path/to/lv-forge with the full path to your checkout. The client launches LV Forge over stdio.
{
"mcpServers": {
"lv-forge": {
"command": "C:/path/to/lv-forge/.venv/Scripts/python.exe",
"args": ["C:/path/to/lv-forge/server.py"]
}
}
}Give your client the absolute paths to the VIs you want to review. For example, ask it to compare examples/Sample_Add.vi and examples/Sample_Multiply.vi, then explain the change inside the loop.
If the offline diagram differs from what you see in LabVIEW, check whether your edits have been saved. If lv_check cannot attach, open LabVIEW and retry. You can pass allow_com_activation: true when COM may launch the registered LabVIEW version.
Save a VI inspection report
Ask the MCP client to call lv_report with the absolute path to a saved VI. Open the returned report_path in a browser and copy the HTML out of the temporary folder if you want to retain it. It includes a UTC timestamp, the saved LabVIEW version when available, detected inputs and outputs, named SubVI calls, the embedded SVG, and any analysis warnings.
Set include_live_check: true to add the IDE's runnability result in a separate section. The report records inspection evidence. Keep functional test results with it when documenting validation.
Known limitations
Partial parses on LabVIEW 2020. LVKit can report a
VITSparse warning on the bundled Add and Multiply VIs while still extracting the diagrams. Larger VIs can produce other parser warnings or fallback control labels. Checkpartial_analysisandwarningsbefore relying on the extracted data.The reported SubVI list can be empty or incomplete. The HTML report lists named calls found in the extracted diagram. Unresolved calls, dynamically selected VIs, and calls omitted by a partial parse can be absent.
lv_checkis limited to the IDE's execution state and associated runnability. It cannot identify the exact broken wire, count broken wires, or detect unsaved diagram edits. See the report's saved-file section for the offline evidence.
Contributing
Useful first contributions include testing the live check across LabVIEW versions and adding reproducible fixture cases for diagram inspection. In bug reports, include Windows and Python versions, LabVIEW version and bitness, the tool and arguments used, and a minimal example you have permission to share.
Run the unit tests from the checkout with .\.venv\Scripts\python.exe -m unittest discover -s tests. The tests mock the LabVIEW connection. They do not require opening or running a VI.
Credits
Harisunder Chidambaram created LV Forge's standalone MCP integration. LV Forge provides the tool interface, input validation, result reporting, and the live Windows LabVIEW check.
OpenAI Codex (ChatGPT's coding agent) helped implement, test, and package the standalone release. Google Antigravity helped investigate and verify LabVIEW 2020 VI Scripting and compatibility in the earlier internal prototype.
PragmaTest and the LVKit contributors provide the offline VI analysis, diff, and renderer through the LVKit dependency.
The MCP Python SDK provides the MCP server interface. pywin32 provides access to Windows COM automation.
Jan Göbel (CalmyJane) created LabVIEW Assistant, which was evaluated during earlier development. The standalone server does not include its code or VIs.
National Instruments provides LabVIEW, its ActiveX interface, and the installed examples used for verification.
LV Forge is distributed under the MIT License.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Change-impact intelligence for tracing dependencies, stale references and required updates.
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Manage SysML2 projects; check, evaluate, verify, query, document and diagram models.
Read title blocks, parts lists, revision history and notes from 2D engineering drawings.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables inspection of existing KiCad boards and schematics — layer/component/net reading, native DRC and ERC, XML netlist generation, Gerber/Excellon export, and GND continuity auditing — plus running LTspice or ngspice simulations with RAW waveform summaries and CSV export. It checks existing designs and preserves artifacts and evidence rather than performing GUI editing, auto-placement, or auto-routing.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables source-preserving import and analysis of EPLAN export reports (devices, connections, PLC I/O, terminals, cables, parts, network, pages) as immutable queryable snapshots, plus inspection of DXF/PDF/DWG drawings and derivation of electrical project evidence. Works offline without EPLAN, supporting querying, duplicate/endpoint checks, revision comparison, and verified JSON export.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read, extend, and validate LabVIEW CSM state-machine VIs, inspecting case branches and exposed APIs, generating modules from official templates, and injecting new states with automatic shift-register and error-cluster tunnel wiring. Also formats complex CSM message arguments, mounts VIs into .lvproj trees, and audits projects for deadlocks, orphan states, and missing documentation.1Mulan Permissive Software , Version 2
- AlicenseAqualityBmaintenanceEnables AI coding agents like Claude Code, Codex, and Cursor to inspect, render, and execute binary NI LabVIEW VIs by driving an installed LabVIEW instance over ActiveX. Returns VI strings, PNG snapshots of diagrams and panels, subVI call trees, and front-panel values from runs.19MIT