Vinv runs, tests, and finds issues in your services — with zero code changes.
Connect Runs on your machine
claude mcp add vinv -e VINV_WORKSPACE=<VINV_WORKSPACE> -- npx -y [email protected]{
"mcpServers": {
"vinv": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"VINV_WORKSPACE": "<VINV_WORKSPACE>"
}
}
}
}{
"mcpServers": {
"vinv": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"VINV_WORKSPACE": "<VINV_WORKSPACE>"
}
}
}
}{
"servers": {
"vinv": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"VINV_WORKSPACE": "<VINV_WORKSPACE>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
VINV_WORKSPACEOptional | Optional override for the repo/workspace Vinv analyzes. Normally unset — the server uses the folder your client exposes via MCP roots, falling back to the current working directory. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 22 Aug 2026 |
| Last updated | 22 Aug 2026 |
| Registry name | io.github.VinvAI/vinv |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.