vmix-workbench-mcp
Related Servers
Alternatives to vmix-workbench-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to control and automate OBS Studio via natural language, covering scenes, sources, audio, recording, streaming, transitions, filters, media playback, diagnostics, and multi-step workflows over the OBS WebSocket protocol.89MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect and control DaVinci Resolve on the local machine, including listing projects, timelines, and media, switching pages, and, when write access is enabled, importing media, building timelines, adding titles and markers, saving projects, and rendering.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a Mac DJ application's decks, mixer, tempo, loops, cues, FX, stems, sampler, Automix, recording, layouts, menus, and music library. It also supports automated transitions between decks and live state feedback.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to control DualStream streaming studio: switch scenes, compose layouts, manage widgets, and react to stream events.30Apache 2.0
- AlicenseAqualityCmaintenanceEnables natural language control of Blackmagic ATEM video switchers via the Model Context Protocol. It allows users to manage camera switching, transitions, audio mixing, macros, and streaming operations through AI assistants.3210MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to DaVinci Resolve Studio to inspect projects and timelines, import media, perform editing operations, adjust clip properties, export timelines, and render frames for visual verification. Includes approval safeguards for destructive actions.MIT
TDQS
Scored across 16 tools
Most tools map to a distinct resource+action pair, and the descriptions are detailed enough to guide selection. The main overlaps are vmix_actions vs. vmix_transition (both can perform transitions) and vmix_scene_create vs. vmix_scene_template (both build scenes).
All tools share the vmix_ prefix and snake_case, and most follow an area_action pattern like vmix_title_update or vmix_trigger_arm. A few bare nouns (vmix_inspect, vmix_actions, vmix_transition, vmix_configuration) and noun-noun names break the otherwise consistent pattern.
16 tools is at the upper edge of acceptable for a vMix workbench covering inspection, operations, actions, scenes, transitions, triggers, assets, and setup guidance. The count is slightly heavy but each tool covers a real part of the workflow.
Core creation and control workflows are well covered, including inputs, scenes, transitions, triggers, and actions. However, there are notable lifecycle gaps: no removal/cleanup for inputs, scenes, assets, or transition presets, and scene creation is one-shot with no update path.