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.

D
Caution
58/100

Bitwig Control Deck

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

⚡ Live Monitored: not connected

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

Is this your MCP?

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.

// key findings
⚠️
Tool descriptions don’t match what handlers do
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 }))
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: CONTROL_DECK_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes34 tools

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_status

Check Control Deck Bridge, Bitwig, the current project, transport, and current selection.

bitwig_actions

Search Bitwig Studio's native action registry by action id, name, or menu text.

bitwig_invoke_action

Invoke one exact Bitwig action id previously returned by bitwig_actions.

bitwig_transport

Read or control Bitwig transport. Tempo changes are read back before success is reported.

bitwig_cue_markers

List Arranger cue markers, or create/update a named marker set at exact beat positions with Bitwig readback verification.

bitwig_tracks

List Bitwig tracks with exact names, positions, safety references, types, and states.

bitwig_track_meters

Read peak signal activity captured for every Bitwig track, or reset the captured maxima before a playback test.

bitwig_plugins

Search Control Deck's local inventory of installed VST3, VST2, Audio Unit, and CLAP plug-ins without opening Bitwig's Browser.

bitwig_refresh_plugin_index

Refresh Control Deck's read-only plug-in inventory after installing or removing audio plug-ins.

bitwig_create_track

Create an empty Bitwig track without opening the Browser or loading any preset.

bitwig_set_track_mix

Set exact mixer values on one verified track and read the resulting state back from Bitwig.

bitwig_rename_track

Rename one verified Bitwig track without changing its audio or MIDI routing.

bitwig_delete_track

Delete one exact track. The supplied name must still match, preventing index drift mistakes.

bitwig_devices

List devices on one exact track. This reads the device chain directly; it does not inspect presets.

bitwig_nest_device

Move one verified top-level device into another device’s native nested chain and verify the resulting parent and child chains.

bitwig_save_device_preset

Open Bitwig’s native Save to Library flow for one verified device and optionally confirm its prefilled name without mouse automation.

bitwig_create_note_clip

Create or replace a launcher MIDI clip on one exact instrument track and write its complete note content.

bitwig_arrange_launcher_clips

Record existing launcher clips into Bitwig's Arranger across exact requested beat regions, merging contiguous regions and restoring the project tempo afterward.

bitwig_clips

List populated launcher clips for one exact track.

bitwig_launch_scene

Launch one Control Deck scene immediately and from the start across all tracks.

bitwig_find_devices

Search Bitwig's Devices browser only. Returns actual device names; presets are excluded by design.

bitwig_insert_device

Insert 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_device

Insert 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_device

Insert 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_samples

Search Bitwig's indexed Samples browser on one exact instrument track.

bitwig_insert_sample

Load one exact indexed sample into a new Bitwig Sampler device at the end of an exact instrument track.

bitwig_insert_sample_file

Load 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_device

Delete one exact device. Both the track and device names must still match.

bitwig_device_parameters

Read a device's full direct parameter list, including third-party plug-ins, with stable IDs and current values.

bitwig_remote_controls

Show 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_controls

Show or hide the compact eight-knob Remote Controls section for the currently selected device, including a device nested inside another device.

bitwig_set_remote_control

Set 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_parameter

Set one device parameter by its stable ID and verify the normalized value through Bitwig readback.

bitwig_open_device_window

Open the native window for one exact device or plug-in.

// known CVEs in dependencies1 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.25.2GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCONTROL_DECK_DASHBOARD_PORT
configCONTROL_DECK_HOST
configCONTROL_DECK_PORT
🔐 secretCONTROL_DECK_TOKEN
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_CONTROL_DECK_API
// quality suggestions

Tool 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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/remymazmanian/bitwig-control-deck?variant=verified)](https://m8ven.ai/mcp/remymazmanian/bitwig-control-deck)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 816f0616fc4b51796216093a70d26ea4726dd10e
code hash: 5e5444291dff096217cdff94fa107c811ca24b4785722571d9f38fa0c4d907a1
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client