mcpField
W
WigAI - Bitwig Studio Extension for AI Control

WigAI - Bitwig Studio Extension for AI Control

Local
github.com/fabbDeveloper Tools62Updated 1w ago
Repository

About WigAI - Bitwig Studio Extension for AI Control

WigAI is a Bitwig Studio extension that exposes playback, device, clip, and scene controls to external AI agents through MCP. The project is archived and no longer maintained.

Key features

  1. 01Start and stop playback
  2. 02Adjust selected device parameters
  3. 03Launch clips and scenes
  4. 04Run as a Bitwig Studio extension

Use cases

  1. 01Start or stop playback with AI commands
  2. 02Change parameters on a selected device
  3. 03Launch clips or scenes from an external agent

MCP support

WigAI implements an MCP server inside the Bitwig Studio extension. External MCP clients connect to its local endpoint to send control commands.

#ai#mcp#bitwig#mcp-server

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

WigAI - Bitwig Studio Extension for AI Control

Warning

This project is archived and no longer maintained. WigAI was a working experiment that I have abandoned. The code is MIT licensed — feel free to fork, reuse and build on it.

Forks with further development (as of October 2026):

  • glassdimly/wigai-full — full project editing: devices, presets, browser, notes, arranger, event streaming
  • jmeachum/WigAI — continued development, clip slot status
  • liqtranq/WigAI — 39 extra MCP tools, resources, project switching
  • 0reo/WigAI — track group hierarchy, arranger clip introspection
  • csabacsaba/WigAI — song structure / scene / cue builder, clip note writing

I am not affiliated with these forks or their authors, have not reviewed their code, and do not endorse them. They are listed for reference only; use them at your own risk. I accept no responsibility or liability for them.

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

  1. Copy the WigAI.bwextension file from build/extensions to your Bitwig Studio extensions directory.
  2. Launch Bitwig Studio
  3. 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!: or BREAKING 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

MIT License

Author

fabb

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.