cvi-mcp
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.
Understand an unfamiliar LabWindows/CVI codebase by asking questions instead of
grepping through fifty files. cvi-mcp replays the preprocessor with the
.prj settings, indexes the compiled C, reconstructs the UI wiring, finds
risks, leaks and dead code, simulates another configuration, looks up the NI
SDK, reports build errors and compares two versions.
It never writes to your sources, the index lives outside the project, and by default no function body ever leaves your machine.
Quick start
pip install -e .
cvi-mcp --check--check prints what your machine actually offers: detected CVI installations
whatever their year, SDK headers, build executable, active settings. It exits
non-zero when something needs your attention !
Then point it at a project and connect it to a client:
export CVI_MCP_PROJECT=/path/to/project # Windows: set CVI_MCP_PROJECT=C:\projects\appConnect it
Claude Code, .mcp.json at the repository root:
{
"mcpServers": {
"cvi": {
"command": "cvi-mcp",
"env": { "CVI_MCP_PROJECT": "C:\\projects\\app" }
}
}
}OpenCode, Claude Desktop and the CLI form are in
Home. Watch out for one trap: OpenCode nests servers under
mcp.servers, takes the command as an array, and names the variables block
environment, not env.
Tools
Group | Tools |
Environment |
|
Reading |
|
Search and impact |
|
Build configuration |
|
User interface |
|
Quality and risks |
|
I/O and persistence |
|
SDK and build |
|
Versions |
|
Every answer is about the code that is actually compiled: #if are evaluated
with the .prj defines and build configuration, and excluded code is set
aside. Long lists are paginated, answers stay under a size budget, and an
empty result says why.
A few answer questions that are otherwise painful. ui_map tells you which
button triggers which callback and what that callback calls. impact gives
the checklist to extend a feature, numbered series to prolong included.
config_diff shows what changes if a macro takes another value, without
touching a file. diff_versions sums up two versions in a few sentences.
How it works
No CVI version is hardcoded. Installations are found by globbing CVI* under
the National Instruments roots and the year is read from the folder name, so
2017, 2019, 2020 and any later release are handled the same way. Sources are
decoded as UTF-8 then cp1252, which is what a French CVI actually writes, and
CRLF and LF produce the same body fingerprint so a file reopened in another
editor does not show up as modified.
Documentation
Three pages per language, no more.
Page | English | Français |
Install, connect, configure | ||
The 38 tools | ||
Design, limits, troubleshooting |
The wiki sources live in wiki/. To publish them:
git clone https://github.com/<owner>/cvi-mcp.wiki.git
cp wiki/*.md cvi-mcp.wiki/ && cd cvi-mcp.wiki && git add . && git commit -m "docs" && git pushExternal references: LabWindows/CVI Help · CVI manuals · MCP · Claude Code MCP · OpenCode MCP · tree-sitter
Development
pip install -e ".[dev]"
pytest
ruff check src tests scriptspytest checks the source tree. To check the shipped artifact instead, build
the archive and run the acceptance recipe: it extracts it, installs into a
clean virtual environment, runs the suite there, then speaks MCP over stdio and
calls the tools for real.
tar czf cvi-mcp.tar.gz cvi-mcp/
python scripts/acceptance.py cvi-mcp.tar.gzEvery file header carries its role, its real state (stable, tolerant or
heuristique) and the package version at its last change.
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
Read-only CVE intelligence, remediation playbooks, and agent setup guides. Not a scanner.
Ask a codebase what calls what: search, blast radius, paths between symbols, and diffs.
Read-only AI coding tools for change verification, release readiness, capacity, and guidance.
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceProvides read-only, provenance-first repository navigation for agents and humans, with ranked lexical retrieval, exact query, document handles, symbol context, and change impact analysis.56 npmApache 2.0- FlicenseNot gradedqualityBmaintenanceEnables coding agents to perform read-only source investigation via a local SQLite index, offering status, search, backlog, context, impact, and drift tools for TypeScript, JavaScript, and Java codebases.-
- AlicenseAqualityBmaintenanceEnables AI coding assistants to query a read-only, locally indexed code graph for who-calls a function, what a function calls, call chains, and where configuration keys are defined or read, returning path:line citations with calibrated confidence and stale-index flags.9MIT
- AlicenseAqualityBmaintenanceEnables users to build and continuously refresh a code index of a repository, then query it to answer architecture, impact, tracing and log questions with verifiable evidence lines. Also checks Java, Kotlin and TypeScript/JavaScript names against real sources and classpaths, and supports commit review and Minecraft/JVM analysis directly from an agent session.51Apache 2.0