vcv-rack-mcp
Related Servers
Alternatives to vcv-rack-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scenes, objects, materials, and renders, download PolyHaven assets, and switch between multiple LLM backends at runtime.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, manage scene objects and materials, render images, fetch PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM providers with runtime switching.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session through scene, object, rendering, and PolyHaven asset tools while sending prompts to a provider-agnostic LLM backend that can be switched at runtime.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect and modify live Blender scenes, manage objects and materials, render images, retrieve PolyHaven assets, and send prompts to configurable local or OpenAI-compatible LLM backends.-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to connect to n8n workflows, Blender 3D, Notion, and filesystem tools through a single MCP hub with hot-pluggable bridges. Features a pedagogical transparency layer for educational purposes and supports multiple LLM providers including Claude, OpenAI, Gemini, and Ollama.6MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to control a live Blender session, inspect and modify scenes, manage PolyHaven assets, render images, and route prompts through configurable local or OpenAI-compatible LLM backends.-
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.