vcv-rack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vcv_patchC | Patch authorship portmanteau — create, edit, validate, list, get, open_in_rack, rack_cycle, import. Return Format{"success": bool, "operation": str, ...operation-specific keys} Examplesvcv_patch(operation="create", name="Ambient Drone", persona="generative", description="slow detuned drone") vcv_patch(operation="validate", patch_id="ambient-drone") vcv_patch(operation="list", persona="generative") |
| vcv_catalogC | Module catalog portmanteau — search, get_module, verify_installed, library_link, sideload, suggest_rack. Return Format{"success": bool, "operation": str, ...operation-specific keys} Examplesvcv_catalog(operation="search", function_tag="osc") vcv_catalog(operation="get_module", plugin_slug="Fundamental", model_slug="VCO") vcv_catalog(operation="suggest_rack", persona_tag="generative", intent="ambient drone") |
| vcv_liveD | Live performance portmanteau — address_map, performance_sheet. Return Format{"success": bool, "operation": str, ...} Examplesvcv_live(operation="address_map", patch_id="ambient-drone") vcv_live(operation="performance_sheet", patch_id="ambient-drone") |
| vcv_agentic_workflowB | SEP-1577 sampling loop: brief -> catalog selection -> generate -> validate -> retry (max 3). Uses ctx.sample when available for autonomous iteration. Falls back to structured result with recovery_options for hosts without sampling. Return Format{"success": bool, "patch_id": str, "iterations": int, "report": list} Examplesvcv_agentic_workflow(brief="slow ambient drone, two detuned voices, filtered noise swells, big reverb") |
| show_patch_cardC | Show a rich in-chat card for a patch. Return FormatToolResult with PrefabApp content. |
| show_catalog_cardC | Show a rich in-chat card for the module catalog. Return FormatToolResult with PrefabApp content. |
| hub_statusA | Show hub status: catalog size, depot health, Rack path. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Prefab Renderer (show_patch_card) | |
| Prefab Renderer (show_catalog_card) |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but the vcv_* portmanteau tools (vcv_catalog, vcv_live, vcv_patch, vcv_agentic_workflow) could cause some confusion as they share a prefix and bundle multiple operations. However, descriptions clarify their domains.
Naming conventions are mixed: snake_case for hub_status and show_* tools, but vcv_* prefix with underscores. The pattern is not uniform, though the vcv_ prefix provides some consistency for the main tools.
Seven tools is well-scoped for a VCV Rack assistant. Each tool covers a distinct area (system status, catalog, patches, live performance, generative workflow), and none feel extraneous.
The tool surface covers core operations: system monitoring, catalog browsing/search/installation, patch management (CRUD), a generative workflow, and live performance. Minor gaps like detailed module parameter control are acceptable for the scope.