Wigai
What is Wigai
WigAI is a Bitwig Controller Extension that acts as a Model Context Protocol (MCP) server, enabling external AI agents to control Bitwig Studio through text-based commands.
Use cases
Use cases include controlling playback during live performances, adjusting device parameters via voice commands, and launching clips and scenes using AI-driven commands.
How to use
To use WigAI, install the extension in Bitwig Studio, activate it in the preferences, and connect an external AI agent to the MCP server endpoint at http://localhost:61169/mcp to send commands and receive responses.
Key features
Key features include MCP server implementation, transport control (start/stop playback), device parameter control for selected devices, and clip and scene launching.
Where to use
WigAI can be used in music production, live performance settings, and any scenario where hands-free control of Bitwig Studio is beneficial through AI assistance.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Overview
What is Wigai
WigAI is a Bitwig Controller Extension that acts as a Model Context Protocol (MCP) server, enabling external AI agents to control Bitwig Studio through text-based commands.
Use cases
Use cases include controlling playback during live performances, adjusting device parameters via voice commands, and launching clips and scenes using AI-driven commands.
How to use
To use WigAI, install the extension in Bitwig Studio, activate it in the preferences, and connect an external AI agent to the MCP server endpoint at http://localhost:61169/mcp to send commands and receive responses.
Key features
Key features include MCP server implementation, transport control (start/stop playback), device parameter control for selected devices, and clip and scene launching.
Where to use
WigAI can be used in music production, live performance settings, and any scenario where hands-free control of Bitwig Studio is beneficial through AI assistance.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Content
WigAI - Bitwig Studio Extension for AI Control
WigAI is a Model Context Protocol (MCP) server implemented as a Bitwig Studio extension. It provides an interface for external AI assistants to control Bitwig Studio through simple text-based commands.
Overview
The extension enables external AI agents (e.g., IDE-based copilots, standalone AI assistants) to interact with and control Bitwig Studio using the Model Context Protocol. This allows for hands-free control via text commands interpreted by an AI assistant.
Key Features
- MCP server implementation
- Transport control (start/stop playback)
- Device parameter control for selected devices
- Clip and scene launching
Requirements
- Bitwig Studio (5.2.7 or later)
- Java 21 LTS
- External AI agent supporting Model Context Protocol
Building
To build the extension:
./gradlew build
This will generate a .bwextension file in the build/extensions directory.
Installation
- Copy the
WigAI.bwextensionfile frombuild/extensionsto your Bitwig Studio extensions directory. - Launch Bitwig Studio
- Open Bitwig preferences, navigate to Extensions, and activate WigAI
Usage
Once the extension is activated in Bitwig Studio, the MCP server will be available at http://localhost:61169/mcp. External AI agents can connect to this endpoint to send commands and receive responses.
Development
This project is developed using the BMAD v2 method with AI Agents. The files in folders agents, ai and docs used for this development method.
Releases
This project uses Nyx for semantic versioning and automated releases. The release process follows Conventional Commits specification:
feat:- new features (minor version bump)fix:- bug fixes (patch version bump)feat!:orBREAKING CHANGE:- breaking changes (major version bump)chore:,docs:,style:,refactor:,test:- no version bump
Releases are automatically created on pushes to the main branch when commits follow the conventional commit format.
License
Author
fabb
Dev Tools Supporting MCP
The following are the main code editors that support the Model Context Protocol. Click the link to visit the official website for more information.
