Bitwig Control Deck (remymazmanian/bitwig-control-deck) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 34 tools. No publisher has claimed this listing.
Local MCP bridge for Bitwig Studio, enabling read-back-verified control of tracks, devices, transport, and plug-in parameters via any MCP client.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
remymazmanian
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
bitwig_statusCheck Control Deck Bridge, Bitwig, the current project, transport, and current selection.
bitwig_actionsSearch Bitwig Studio's native action registry by action id, name, or menu text.
bitwig_invoke_actionInvoke one exact Bitwig action id previously returned by bitwig_actions.
bitwig_transportRead or control Bitwig transport. Tempo changes are read back before success is reported.
bitwig_cue_markersList Arranger cue markers, or create/update a named marker set at exact beat positions with Bitwig readback verification.
bitwig_tracksList Bitwig tracks with exact names, positions, safety references, types, and states.
bitwig_track_metersRead peak signal activity captured for every Bitwig track, or reset the captured maxima before a playback test.
bitwig_pluginsSearch Control Deck's local inventory of installed VST3, VST2, Audio Unit, and CLAP plug-ins without opening Bitwig's Browser.
bitwig_refresh_plugin_indexRefresh Control Deck's read-only plug-in inventory after installing or removing audio plug-ins.
bitwig_create_trackCreate an empty Bitwig track without opening the Browser or loading any preset.
bitwig_set_track_mixSet exact mixer values on one verified track and read the resulting state back from Bitwig.
bitwig_rename_trackRename one verified Bitwig track without changing its audio or MIDI routing.
bitwig_delete_trackDelete one exact track. The supplied name must still match, preventing index drift mistakes.
bitwig_devicesList devices on one exact track. This reads the device chain directly; it does not inspect presets.
bitwig_nest_deviceMove one verified top-level device into another device’s native nested chain and verify the resulting parent and child chains.
bitwig_save_device_presetOpen Bitwig’s native Save to Library flow for one verified device and optionally confirm its prefilled name without mouse automation.
bitwig_create_note_clipCreate or replace a launcher MIDI clip on one exact instrument track and write its complete note content.
bitwig_arrange_launcher_clipsRecord existing launcher clips into Bitwig's Arranger across exact requested beat regions, merging contiguous regions and restoring the project tempo afterward.
bitwig_clipsList populated launcher clips for one exact track.
bitwig_launch_sceneLaunch one Control Deck scene immediately and from the start across all tracks.
bitwig_find_devicesSearch Bitwig's Devices browser only. Returns actual device names; presets are excluded by design.
bitwig_insert_deviceInsert one exact device at the end of an exact track. Only the Devices session is scanned; insertion is refused if the name is ambiguous.
bitwig_insert_stock_deviceInsert a stock Bitwig device by its stable UUID, optionally immediately before one verified device. This supports valid note-processing positions that Bitwig's end-of-chain Browser omits.
bitwig_insert_clap_deviceInsert a CLAP plug-in directly by its stable ID, optionally immediately before one verified device, bypassing Bitwig Browser filters and redundant-format hiding.
bitwig_find_samplesSearch Bitwig's indexed Samples browser on one exact instrument track.
bitwig_insert_sampleLoad one exact indexed sample into a new Bitwig Sampler device at the end of an exact instrument track.
bitwig_insert_sample_fileLoad an absolute WAV, AIFF, or FLAC file path into a new Bitwig Sampler device on an exact instrument track and verify the loaded sample name.
bitwig_delete_deviceDelete one exact device. Both the track and device names must still match.
bitwig_device_parametersRead a device's full direct parameter list, including third-party plug-ins, with stable IDs and current values.
bitwig_remote_controlsShow Bitwig’s compact eight-knob Remote Controls section for one exact device, hide its long generic parameter list, and optionally select a named page.
bitwig_selected_device_remote_controlsShow or hide the compact eight-knob Remote Controls section for the currently selected device, including a device nested inside another device.
bitwig_set_remote_controlSet one visible Bitwig Remote Control by page and control name, using the same native parameter path as the on-screen knobs, then verify the value.
bitwig_set_device_parameterSet one device parameter by its stable ID and verify the normalized value through Bitwig readback.
bitwig_open_device_windowOpen the native window for one exact device or plug-in.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
CONTROL_DECK_DASHBOARD_PORTCONTROL_DECK_HOSTCONTROL_DECK_PORTCONTROL_DECK_TOKENNEXT_PUBLIC_CONTROL_DECK_APITool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
34/34 tools missing one or more hints — bitwig_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bitwig_actions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bitwig_invoke_action (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +31 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Descriptions match behaviour
14 tools describe read intent but their handlers mutate — bitwig_status (line 36: mkdir(logDirectory, { recursive: true })); bitwig_actions (line 36: mkdir(logDirectory, { recursive: true })); bitwig_transport (line 36: mkdir(logDirectory, { recursive: true }))
Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.
Tool inputs are validated
26/34 tool handlers declare input schemas (76%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@1.25.2 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Tool description accuracy
14 tools have description/behavior mismatches: bitwig_status: description implies read-only but handler writes/deletes/executes; bitwig_actions: description implies read-only but handler writes/deletes/executes; bitwig_transport: description implies read-only but handler writes/deletes/executes
Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/remymazmanian/bitwig-control-deck)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check