WigAI MCP Server

WigAI MCP server exists for a simple reason — assistants are far more useful when they can act on WigAI directly instead of describing what you should do. Bitwig Controller Extension that provides an MCP Server for AI Agent control.

What you get

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.

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.

• MCP server implementation
• Transport control (start/stop playback)
• Device parameter control for selected devices
• Clip and scene launching

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

• Bitwig Studio (5.2.7 or later) - Java 21 LTS - External AI agent supporting Model Context Protocol

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by fabb; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against WigAI's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the wigai mcp server does with a few real requests.