NIGEL limitations and LabVIEW-MCP Preview

[Cloedu72]

Hello Forum and NI

I'm curious to know when there will be any changes to Nigel's limitations. Right now, the biggest issue for me is that you can't use your own SubVis when generating code!
=> Are there any concrete plans (roadmap) for this?

I’ve created my own MCP, which has exactly the same limitations as Nigel’s. If anyone’s interested, you can download an early beta version here.

https://github.com/Zuehlke/labview-mcp

https://github.com/Zuehlke/labview-mcp/releases

The LabVIEW-MCP code generation, documentation, etc., work wonderfully, but with these limitations, I don't want to officially release it!

=> By the way, the project is exactly 1 day old. I created the MCP in a single day and configured all the properties of the VIs, etc.! 😁

Here a list of the current Nigel limitations (LV2026 Q3)

Best

Claude

[pawhan11]

Super nice !

[Cloedu72]

I released the first official beta version of LabVIEW-MCP today! The limitations mentioned above still apply, but as long as you use VIs from the LabVIEW subfolders, everything works!

I’m also looking for beta testers to take a closer look at the functionality.

As another use case, I’ve created a draft for a documentation agent. The idea is similar to Antidoc, in that everything is documented. However, in addition, a comment is automatically added to VIs without a description based on the implemented function!
https://github.com/Zuehlke/labview-mcp
https://github.com/Zuehlke/labview-mcp/releases

For example, you could create the following VI as a basic test:

  

=> Controls and Indicators are generated as Icons (can (currently) not be changed)

The latest version adds corresponding VI-Icons (example for Hello World VI)

In addition, it should also be possible to generate projects, libraries, and classes.

But everything is still pretty new and hasn't been tested much! 🙂

I use Claude Code with Opus 5. However, it should also work with other LLMs. Here are the settings for Claude Code:

{

   "mcpServers": {
      "labview": {
         "command": "C:\\YourFolderName\\LabVIEWMCP.exe",
         "args": [],
         "env": {}
      }
   }
}

Have fun

Claude

[Cloedu72]

As a little weekend treat, I've created a new version.
The latest version includes agents that automatically scan the examples and the palette for reusable code snippets.
There are now agents for the following tasks:

• Creating a new VI with an icon and help text
• Editing an existing VI
• Creating Documentation for a Project (Similar to AntiDoc)

https://github.com/Zuehlke/labview-mcp

https://github.com/Zuehlke/labview-mcp/releases/tag/V0.4.0

The focus is now on optimization! (Speed and token consumption)

=> Most of the restrictions in the table still apply 😞

Best

Claude

[Cloedu72]

The latest versions are primarily optimized for performance. The XML fragments are now stored in a cache, and the more you use the MCP, the faster the generation process becomes.

Here's an example of what it might look like right now:

-----------------------------------------------------------------------------------------

Prompt:

Create a VI for me with the following properties: We'll create a VI that loads an analog signal from a CSV file and then displays it.

Input:

* File name

Function:

* Load the CSV file containing the signal

* Convert the signal to a waveform

* Display the signal

Output:

* Waveform signal

* Boolean indicating whether the file was loaded successfully

* Error status Save as: C:\temp\SignalLoader_new.vi

-----------------------------------------------------------------------------------------

Fully developed, including the icon, VI description, and various tests (with generated csv file).

=> Time required: 4.5 minutes (Opus5 Effort=Low)

 

Example Claude Effort=Medium (generates even smarter VIs)

[Cloedu72]

Due to a request from NI R&D this repo has been taken offline. Feel free to leave a comment if you need further information.

[Cloedu72]

Hello Forum and NI

I’m officially authorized to make the GIT repo public again! Thank you very much, NI, for allowing us to continue developing this tool for the LabVIEW community. 🙂
=> The repo will be public again tomorrow 🙂

Best

Claude