bitwig

This MCP server provides programmatic control of Bitwig Studio through Claude via the MCP interface. It exposes tools to control transport (play, stop, set_tempo), track parameters (volume, pan, mute), device parameters, and fetch project/track information. You can query project state, adjust mixer and device settings, and trigger workflow templates via the included commands. To use it, first ensure Bitwig Studio is configured to receive OSC/Open Sound Control messages, then run the Python MCP server and connect Claude Desktop to the Bitwig MCP server. The available tools map to Bitwig actions, enabling Claude to orchestrate mixing sessions, automate device parameter changes, and retrieve project data for informed decision making.

Prerequisites:

• Python 3.10+
• Bitwig Studio 5.2+ with Driven by Moss integration
• Claude Desktop app with MCP support

Install from GitHub:

# Clone the repository
git clone https://github.com/jxstanford/bitwig-mcp-server.git
cd bitwig-mcp-server

# Install dependencies (via uv, as documented by the project)
uv sync

Run the server (examples):

# Run with default settings
python -m bitwig_mcp_server

# Run with custom settings
python -m bitwig_mcp_server --host 127.0.0.1 --send-port 8000 --receive-port 9000 --transport stdio --debug

Claude Desktop installation:

# Install the server in Claude Desktop
mcp install bitwig_mcp_server/__main__.py

Then open Claude Desktop and select the Bitwig MCP Server from the MCP Servers dropdown.

Tips and notes:

• Ensure OSC receive/send ports align between Bitwig and the MCP server (default receive: 8000, send: 9000).
• The server relies on OSC, so confirm Bitwig is configured to accept OSC messages from the MCP server.
• Environment variables (HOST, PORTs, TRANSPORT, DEBUG) can be used to customize runtime behavior; provide sensible defaults if not overriding.
• Typical workflow involves configuring a virtual MIDI/OSC device in Bitwig, installing Driven by Moss, and then launching the MCP server so Claude can issue commands like play, set_tempo, set_track_volume, or get_project_info.
• Development and testing can be performed without Bitwig by using unit tests; integration tests require a running Bitwig Studio with OSC enabled.