vcvpatch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RACK_USER_DIR | No | Override the Rack user directory path (defaults to ~/Library/Application Support/Rack2 on macOS, %LOCALAPPDATA%\Rack2 on Windows, ~/.local/share/Rack2 on Linux). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vcv_readA | Read a .vcv file: Rack version, modules, cables, asset list and a text summary. |
| vcv_writeA | Write a full patch.json dict to a .vcv file. Validates first; refuses to overwrite unless overwrite=true. Pass keep_assets_from=<original .vcv> when saving an edited copy so module asset files are preserved. |
| vcv_createA | Create a new .vcv file from a list of modules and cables. Module ids, plugin versions and positions are filled in automatically. Cables reference modules by their index in the modules list. |
| vcv_validateA | Check a .vcv file for structural problems and missing plugins. |
| vcv_library_searchA | Search modules installed in the local Rack library by free text and/or tags. Returns exact plugin/model slugs to use in vcv_create. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: read, write, create, validate, and library search. Even where read and validate both touch .vcv files, one provides a summary while the other checks structural integrity, so there is no real ambiguity.
All tools share the vcv_ prefix and use lowercase snake_case, which is consistent. The only minor deviation is vcv_library_search, which is object-verb rather than the verb-first pattern used by the other four tools.
Five tools is well-scoped for a patch-file manipulation server. Each tool covers a necessary operation without redundancy or bloat.
The toolset covers the full patch lifecycle: create, read, write, validate, and search for library modules needed during creation. There are no obvious dead ends or missing core operations.