LabVIEW MCP
MCP serverCommunity
A Windows MCP server with 118 tools that reads, generates, edits and runs LabVIEW VIs from a running LabVIEW 2020 or newer. By Zühlke.
111 starsUpdated 1 day agoGitHub data from 5 Nov 2026
At a glance
- Type
- MCP server
- Works with
- LabVIEW
- How it connects
- Drives a running copy of the tool
- Access
- Can modify models
- Tool versions
- LabVIEW 2020 or newer; NI's own gRPC AI service on LabVIEW 2026 Q3, ActiveX and pylabview on older versions
- Operating systems
- Windows
- Needs a LabVIEW licence
- Yes
- Transport
- Local (stdio)
- AI clients documented
- Claude Code, Claude Desktop, Cursor, Codex, GitHub Copilot
- Licence
- MIT
- Language
- Python
What it can do
- Returns a VI's block diagram, or a whole .lvproj or .lvlib, as text so the agent can explain it.
- Generates new VIs from the AIXML text format, validates them and saves real binary .vi files, then runs a VI as top level and reads its outputs back.
- Edits existing VIs byte for byte through a bundled copy of pylabview, which also works without LabVIEW or a licence.
- Searches installed palettes and NI's shipping examples, runs build specifications, and ships Claude Code agents for VI generation, editing, documentation, classes, DQMH modules and unit tests.
Limitations
- The authors call it research-grade: write tools overwrite a VI without asking, and regenerating a VI loses its layout, decorations and icon.
- The lvai gRPC interface it uses on LabVIEW 2026 Q3 is not a published NI API and may change with any LabVIEW update.
- Windows x64 only; not affiliated with NI or Emerson.
Install
claude plugin marketplace add Zuehlke/labview-mcp
claude plugin install labview-mcp@zuehlke-labviewSource: github.com/Zuehlke/labview-mcp#installation-with-claude-code
MCP servers and skills run code on your computer. Review the source before installing.
AI-generated models, drawings and results must be checked by a qualified engineer before use.