LabVIEW Toolkit
a toolkit to host mcp servers from LabVIEW.
What is LabVIEW Toolkit?
LabVIEW Toolkit is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to toolkit to host mcp servers from labview.
a toolkit to host mcp servers from LabVIEW.
This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.
Features
- a toolkit to host mcp servers from LabVIEW.
Use Cases
Maintainer
Works with
Installation
Manual Installation
npx labview-mcp-server-toolkitConfiguration
Configuration Details
claude_desktop_config.json
Performance
Response Metrics
Resource Usage
How to Set Up and Use LabVIEW Toolkit
The LabVIEW MCP Server Toolkit lets you host MCP servers directly from LabVIEW applications, exposing LabVIEW VIs as tools, prompts, and resources that AI assistants like Claude or ChatGPT can call during a conversation. It runs an HTTP server inside LabVIEW that speaks JSON-RPC 2.0, enabling LLMs to control instrumentation, test equipment, and automation workflows in real time. Engineers building automated test systems or data acquisition pipelines can use this toolkit to add AI-driven control without rewriting their existing LabVIEW code.
Prerequisites
- National Instruments LabVIEW installed (any recent version supporting VI Packages)
- IG HTTP Server Toolkit installed via VIPM (vipm.io/package/illuminatedg_lib_ig_http_server/)
- JKI JSONtext installed via VIPM (vipm.io/package/jdp_science_jsontext/)
- An MCP-compatible client such as Claude Desktop that supports mcp-remote over HTTP
- mcp-remote npm package available (installed via npx)
Install the required LabVIEW dependencies
The toolkit depends on two VIPM packages: IG HTTP Server Toolkit for the HTTP transport layer and JKI JSONtext for JSON-RPC serialization. Install both from VI Package Manager before opening the toolkit.
Open and configure the LabVIEW MCP Server Toolkit
Download the toolkit from the GitHub repository and open the main VI in LabVIEW. Configure the listening port (default 36987) and register the VIs you want to expose as MCP tools, prompts, or resources.
Define your tools in LabVIEW
Wrap your instrument-control or data-acquisition VIs as MCP tools. Each tool needs a name, description (used by the LLM to decide when to call it), and typed inputs and outputs. Supported input types are String, Number, and Boolean.
Run the LabVIEW HTTP server
Execute the main toolkit VI to start the MCP HTTP server. By default it listens on port 36987. The server exposes the /mcp/server endpoint that MCP clients connect to.
Configure your MCP client to connect
Because the LabVIEW server uses HTTP rather than stdio, configure Claude Desktop to connect via the mcp-remote proxy. Adjust the port number if you changed the default.
{
"mcpServers": {
"labview-mcp-server": {
"command": "npx",
"args": [
"mcp-remote",
"http://127.0.0.1:36987/mcp/server"
]
}
}
}Restart Claude Desktop and verify
Claude Desktop reads tool lists at startup. Close the app completely (including the taskbar icon) and reopen it. Ask Claude to list available tools — your LabVIEW VIs should appear by the names you configured.
LabVIEW Toolkit Examples
Client configuration
Claude Desktop configuration using mcp-remote to connect to the LabVIEW HTTP server running on localhost. Change the port number to match your LabVIEW server configuration.
{
"mcpServers": {
"labview-mcp-server": {
"command": "npx",
"args": [
"mcp-remote",
"http://127.0.0.1:36987/mcp/server"
]
}
}
}Prompts to try
Sample prompts for controlling LabVIEW instruments and automation through Claude once your VIs are registered as MCP tools.
- "Run the temperature measurement VI and return the current reading from channel AI0"
- "What LabVIEW tools are available to me right now?"
- "Execute the motor control VI to set speed to 1500 RPM and direction to forward"
- "Read the last 100 samples from the data acquisition VI and summarize the trend"Troubleshooting LabVIEW Toolkit
Claude Desktop does not see any LabVIEW tools after configuration
Claude Desktop only retrieves the tool list at startup. You must fully close Claude Desktop (including the system tray icon) and reopen it after the LabVIEW server is already running. Multiple restarts may be needed the first time.
mcp-remote connection fails with ECONNREFUSED
The LabVIEW HTTP server must be running before Claude Desktop starts. Run the main toolkit VI in LabVIEW first, confirm it shows as running, then launch Claude Desktop. Check that the port in your config matches the port configured in the LabVIEW VI.
VI outputs are missing or malformed in tool responses
All outputs from LabVIEW tools are flattened to JSON. Complex LabVIEW data types (clusters, arrays) are serialized automatically, but only String, Number, and Boolean are supported as tool inputs. Wrap complex input types as JSON strings and parse them inside the VI.
Frequently Asked Questions about LabVIEW Toolkit
What is LabVIEW Toolkit?
LabVIEW Toolkit is a Model Context Protocol (MCP) server that toolkit to host mcp servers from labview. It connects AI assistants to external tools and data sources through a standardized interface.
How do I install LabVIEW Toolkit?
Follow the installation instructions on the LabVIEW Toolkit GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.
Which AI clients work with LabVIEW Toolkit?
LabVIEW Toolkit works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.
Is LabVIEW Toolkit free to use?
Yes, LabVIEW Toolkit is open source and available under the MIT license. You can use it freely in both personal and commercial projects.
LabVIEW Toolkit Alternatives — Similar Developer Tools Servers
Looking for alternatives to LabVIEW Toolkit? Here are other popular developer tools servers you can use with Claude, Cursor, and VS Code.
Ecc
★ 188.2kThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Javaguide
★ 155.8kJava 面试 & 后端通用面试指南，覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Gemini CLI
★ 104.5kA secure MCP server that wraps the Google Gemini CLI, allowing clients to query Gemini models using local OAuth sessions without requiring an API key. It provides tools for model interaction and diagnostics with built-in protection against command in
Awesome MCP Servers
★ 87.3k⭐ Curated list of Model Context Protocol (MCP) servers - tools that extend Claude Desktop, Cursor, Windsurf, and other MCP clients with custom capabilities.
MCP Servers
★ 86.0kModel Context Protocol Servers
CC Switch
★ 77.5kA cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Gemini CLI & Hermes Agent. Only official website: ccswitch.io
Browse More Developer Tools MCP Servers
Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.
Set Up LabVIEW Toolkit in Your Editor
Choose your AI client for step-by-step setup instructions.
Quick Config Preview
Add this to your claude_desktop_config.json or .cursor/mcp.json
Ready to use LabVIEW Toolkit?
Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.