vcvpatch
Related Servers
Alternatives to vcvpatch
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to discover running VCV Rack instances, inspect and validate patches, apply structured changes atomically with confirmation, manage patch files with checkpoints, and read signal telemetry via a secure local loopback bridge.1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and export OpenPencil .fig and .pen files directly from disk, supporting operations like info, tree traversal, XPath queries, linting, and conversion to various formats without the desktop app or CLI.MIT
- AlicenseNot gradedqualityAmaintenanceEnables reading, querying, and editing Node-RED flows.json files through MCP, providing tools for node management, layout validation, and deployment.MIT
- AlicenseCqualityBmaintenanceEnables LLMs to compose VCV Rack modular synth patches by generating plain JSON, with tools for patch creation, catalog search, and live OSC control.75MIT
- FlicenseAqualityDmaintenanceEnables AI-powered manipulation of Cardinal/VCV Rack modular synthesizer patches, allowing users to create, analyze, modify, and connect modules and cables through natural language.7-
- AlicenseAqualityCmaintenanceMCP server for on-disk patching of binary artifacts with SHA-256 manifest, byte-level patch application, and manifest-driven restore, ensuring auditability and reversibility.4MIT
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.