beat-twin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITWIG_HOST | No | The host of the Bitwig controller JSON-RPC bridge. | 127.0.0.1 |
| BITWIG_PORT | No | The port of the Bitwig controller JSON-RPC bridge. | 8888 |
| BITWIG_MCP_WRITE_POLICY | No | Comma-separated list of write classes to enable (e.g., 'transport,mixer_write'). | |
| BITWIG_MCP_ENABLE_WRITES | No | Set to '1' to enable every write class. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bitwig_session_inspectA | [policy:read] Read-only inspection of Bitwig transport, tracks, scenes, selected device, and remote controls |
| bitwig_arrangement_planB | [policy:read] Plan-only arrangement suggestion from the read-only Bitwig session snapshot |
| transport_get_tempoA | [policy:read] Get the current tempo (BPM) |
| transport_get_positionA | [policy:read] Get current playhead position in beats |
| transport_playing_statusA | [policy:read] Check if transport is currently playing |
| track_bank_get_statusA | [policy:read] Get status (vol/pan/mute/solo) of all 8 tracks in the current bank window |
| scene_listB | [policy:read] List available scenes in the current bank |
| clip_get_infoA | [policy:read] Get loop and playing-step info for the focused cursor clip |
| track_selected_get_statusA | [policy:read] Get status of the currently selected track |
| device_get_statusA | [policy:read] Get status of the currently selected device |
| device_get_remote_controlsA | [policy:read] Get the 8 remote control parameters for the current page |
| device_listB | [policy:read] List devices on a visible track |
| browser_get_statusB | [policy:read] Get the Bitwig popup browser status |
| browser_list_resultsA | [policy:read] List visible results in Bitwig's popup browser |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools target distinct resources (arrangement, session, browser, clip, device, scene, track, transport), but 'bitwig_session_inspect' is broad and could overlap with track/device status tools, though descriptions clarify its role.
All tools follow a consistent pattern: domain prefix (bitwig_, browser_, clip_, etc.) plus descriptive snake_case verb phrase, making the surface predictable and easy to navigate.
With 14 tools covering key aspects of a DAW (arrangement, transport, tracks, devices, clips, browser), the count is well-scoped for a read-only integration.
The read-only surface covers inspection of many elements, but lacks write/mutate tools for actual control, and the 'plan' tool suggests a gap where no apply tool exists.