WigAI
Bitwig Controller Extension that provides an MCP Server for AI Agent control
claude mcp add --transport stdio fabb-wigai node path/to/WigAI/server.js \ --env BITWIG_EXTENSION_HOME="Path to WigAI Bitwig extension home directory (optional placeholder)"
How to use
WigAI is an MCP server implemented as a Bitwig Studio extension. It exposes an HTTP-based MCP endpoint at http://localhost:61169/mcp that external AI agents can connect to in order to control Bitwig Studio through simple text-based commands. The server supports common MCP interactions such as transport control (start/stop playback), adjusting device parameters on selected devices, and launching clips or scenes. To use WigAI, ensure Bitwig Studio is installed and the WigAI extension is loaded and activated within Bitwig's Extensions preferences. Once active, connect your external AI agent to the MCP endpoint and begin issuing textual commands that WigAI will interpret and translate into Bitwig API actions.
How to install
Prerequisites:
- Bitwig Studio (5.2.7 or later)
- Java 21 LTS
- Gradle wrapper available in the project
Installation steps:
- Clone the WigAI repository to your development machine.
- Open a terminal in the repository root and build the extension: ./gradlew build
- Locate the generated WigAI extension file (WigAI.bwextension) in build/extensions.
- Copy WigAI.bwextension to Bitwig Studio's extensions directory:
- On Windows: C:\Users<YourUser>\AppData\Roaming\Bitwig Studio\extensions
- On macOS: /Users/<YourUser>/Library/Bitwig Studio/extensions
- On Linux: ~/. Bitwig Studio/extensions
- Launch Bitwig Studio, go to Preferences > Extensions, and enable WigAI.
- WigAI will start and expose the MCP endpoint at http://localhost:61169/mcp once loaded.
Additional notes
Notes and tips:
- Ensure Bitwig Studio is running before starting WigAI.
- The MCP endpoint is hosted by the WigAI extension and Bindings may require network whitelisting if using a containerized environment.
- If you encounter connection issues, verify that Bitwig Studio is listening on the expected port (61169 by default) and that the WigAI extension is active in the Extensions list.
- WigAI relies on the Model Context Protocol; ensure your external AI agent supports MCP commands and adheres to the protocol for command structure and responses.
- This project uses the BMAD v2 method for AI agent integration and includes folders agents, ai, and docs used during development.
Related MCP Servers
jadx-ai
Plugin for JADX to integrate MCP server
sonarqube
SonarQube MCP Server
PIXRA
Pixelize the real world on-chain
discord
A MCP server for the Discord integration. Enable your AI assistants to seamlessly interact with Discord. Enhance your Discord experience with powerful automation capabilities.
api2mcp4j
This is a revolutionary AI MCP plugin with excellent pluggable and encapsulated features. With just a few lines of configuration, it can easily integrate into your Spring boot web program and give it MCP capabilities,inheriting the powerful engineering capabilities of the Spring series framework
quarkus-workshop-langchain4j
Quarkus Langchain4J Workshop