Can AI agents automate NI LabVIEW?

LabVIEW is automatable today through the first-party VI Server and the Windows ActiveX automation server, which open application and VI references, get or set properties, invoke methods, and run VIs from LabVIEW or from external COM clients such as Python via win32com Dispatch("Labview.Application"). Full and Professional editions can also publish selected VIs as RESTful HTTP method services. Official .NET Framework assemblies and shared libraries export chosen VIs for C# or C callers, but those builds need Application Builder (Professional, or the module sold separately) and a matching LabVIEW Runtime on each target. A deployment license is required per computer that runs distributed applications. The LabVIEWCLI package runs MassCompile, ExecuteBuildSpec, RunVI, CloseLabVIEW, and related operations, including headless CI that does not need an active LabVIEW license; RunVI only accepts VIs with a documented connector pane. NI Nigel AI is an in-IDE assistant, not a first-party MCP server for automating LabVIEW. LabVIEW 2026 Q3 documents that Nigel can connect to MCP servers as a client. Zapier, Make, Power Automate, and n8n catalogs were not opened. Computer-use viability is unassessed. NI TestStand and the LabVIEW+ Suite companion products are out of scope.

Best path today: api · Overall automatability: 6/10