1. Conduid
  2. Developer Tools
  3. Bitwig MCP Server
MCP server · Developer Tools

Bitwig MCP Server

MCP Server for Bitwig Studio

Unclaimed MIT last commit a year ago devtools
54Fair

Scored 5 months ago · breakdown

About Bitwig MCP Server

Bitwig MCP Server is an MCP server published by WeModulate in the Developer Tools category: mCP Server for Bitwig Studio.

The repository has 76 stars and 13 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/WeModulate/bitwig-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Bitwig MCP Server

Powered by Claude · Grounded in docs

I know everything about Bitwig MCP Server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • ✓Tests presentA test suite exists in the repository.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Bitwig MCP Server

Release Build status codecov License

A Model Context Protocol (MCP) server for Bitwig Studio that allows Claude to control your DAW.

Warning! This is a work in progress. Documentation and implementation may be out of sync, and not all functionality may work as expected.

Features

  • AI-Powered Music Production: Control Bitwig Studio with Claude via MCP
  • Transport Controls: Play, stop, and set tempo
  • Mixer Controls: Adjust volume, pan, and mute/unmute tracks
  • Device Controls: Manipulate device parameters
  • Project Information: Access track and device information
  • Templates and Prompts: Pre-configured workflows for common tasks

Installation

Prerequisites

Install from GitHub

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

# Install dependencies
uv sync

Usage

1. Configure Bitwig Studio

  1. If necessary, add a virtual MIDI device for OSC
  2. Follow Driven by Moss installation instructions for Bitwig 5.2+
  3. Open or restart Bitwig Studio
  4. Go to Settings > Controllers
  5. Click "Add Controller" and select "Open Sound Control" and "OSC"
  6. Configure the receive port (default: 8000) and send port (default: 9000)
  7. Enable the controller

2. Run the Bitwig MCP Server

# Run the server with default settings
python -m bitwig_mcp_server

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

3. Add to Claude Desktop

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

Available Tools

The Bitwig MCP Server provides the following tools:

Transport Controls

  • play: Toggle play/pause state or set it to a specific state
  • stop: Stop playback
  • set_tempo: Set the tempo in beats per minute

Track Controls

  • set_track_volume: Set track volume (0-128)
  • set_track_pan: Set track pan position (0-128)
  • set_track_mute: Mute, unmute, or toggle mute state for a track

Device Controls

  • set_device_parameter: Set a device parameter value (0-128)

Information

  • get_project_info: Get information about the current Bitwig project
  • get_tracks_info: Get information about all tracks in the project
  • get_track_info: Get information about a specific track
  • get_device_parameters: Get information about the selected device parameters

Available Resources

  • bitwig://project/info: Project information
  • bitwig://transport: Transport state
  • bitwig://tracks: All tracks in the project
  • bitwig://track/{index}: Specific track information
  • bitwig://devices: Active devices
  • bitwig://device/parameters: Parameters for the selected device

Example Prompts

  • setup_mixing_session: Set up a new mixing session with default settings
  • create_track_template: Create a track template with specific devices and settings
  • optimize_track_settings: Get recommendations for optimizing track settings

Configuration

The server can be configured through:

  1. Environment variables or .env file
  2. Command line arguments
  3. Settings in bitwig_mcp_server/settings.py

Command Line Arguments

python -m bitwig_mcp_server --help

Development

Environment Setup

# Install dev dependencies
uv sync

# Install pre-commit hooks
uv run pre-commit install

Running Tests

# Run unit tests (no Bitwig required)
make test

# Run all tests including Bitwig integration tests
# (requires Bitwig Studio running with OSC enabled)
make test-all

Code Quality

# Run code quality checks
make check

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgements

Thanks to Jürgen Moßgraber for publishing the Driven by Moss package. This package leverages that package to interact with Bitwig.

README fetched from the repository 6 days ago. The original is authoritative.

Questions

About Bitwig MCP Server

How do I install Bitwig MCP Server?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Bitwig MCP Server safe to use with an AI agent?

Its trust score is 54 out of 100 (fair). It passes 5 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Bitwig MCP Server still maintained?

The last commit was a year ago and 1 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.