Version 0.2.0
On this page
This page identifies the extension/Python package version. It is not a capability guarantee and it is not a live-session acceptance report.
The current source registers 57 MCP tools across native host/Grid helpers,
preview-first sessions, offline composition, and offline audio-file analysis.
The running server's tools/list response is authoritative. Older descriptions
of 31 or 90 tools are historical and must not be used as the current contract.
Compatibility
| Version | What it identifies |
|---|---|
| 0.2.0 | Bridge extension and Python package; not a capability guarantee |
| Bitwig Studio 6.1.1 | Exact private runtime target, additionally checked against native method signatures |
| Controller API 25 | Public minimum API and compile-time dependency |
| Protocol 4 | Local text-command/JSON-response socket protocol |
The extension binds locally at 127.0.0.1:8765 when running and claims no MIDI
ports. Matching the public API number does not establish private native
compatibility. Unknown versions or layouts fail closed; public host controls
can still operate when a selected Grid graph is unavailable.
The previously published v0.2.0 extension may contain stale private bindings. Build this checkout when the current native runtime is required; a copied bundle is not proof that the running controller loaded it. Save work and restart Bitwig deliberately after replacement, then check protocol 4 and the capability flags. A public ControllerHost restart can retain an old class definition in the same macOS session.
Current implemented families
The source-level MCP surface includes:
- read-only song/transport, track, mix, device, action, selected-device, Grid graph, catalog, and display-value-resolution helpers;
- guarded transport, track arm/mute, mix gain/pan/send, device insertion/removal, and graph edit/move/clear operations;
- Grid topology analysis, staged patch steps, scoped parameter restore, and shaping sessions;
- offline Type-1 MIDI planning/revision/export with digest-bound manifests; and
- offline audio-file analysis and attenuation-only RMS comparison.
Native public writes are submitted/immediate proxy operations. A fresh read-back is required before treating transport, track, mix, device, or other host state as complete. Graph edits require exact graph identity/revision and explicit authorization.
Historical observations
Earlier decoded notes recorded a Grid catalog and modulation inventory and exercised native graph operations on one Apple Silicon/macOS session. Those records are historical reference material, not current live acceptance, and do not establish support for every catalog entry, another Bitwig build, another platform, save/reopen persistence, audio output, or listening quality.
Do not turn an inventory count into a hardcoded test or acceptance claim. Read
the live native capabilities and MCP tools/list responses instead.
Support boundaries
The bridge does not implement:
- native arranger note, clip, or automation editing;
- MIDI import or voice realization;
- live capture;
- audio rendering/export; or
- project save, new, load, or delivery.
Offline MIDI is an artifact, not an imported project or voice realization. Offline audio analysis is file-based, not a recorder or Bitwig renderer. Native undo/redo is host-wide; shaping undo and patch restore are narrower and do not replace a backup.
Upgrade
- Save work, build the intended checkout, and install using the installation guide.
- Restart Bitwig deliberately after replacement; do not assume a copied file or public ControllerHost restart reloaded the classes.
- Confirm native protocol 4, host identity, and required capability flags.
- Restart/reconnect MCP from the intended checkout and inspect its actual
tools/listresponse. - Re-read project, selection, mix, and graph identities. Do not reuse stale session revisions, snapshots, or module identities across a restart.
- Never retry an ambiguous write without a fresh read-back.