WigAI - Bitwig Studio Extension for AI Control

Created By
fabba year ago
Bitwig Controller Extension that provides an MCP Server for AI Agent control
Overview

what is WigAI?

WigAI is a Bitwig Studio extension that acts as a Model Context Protocol (MCP) server, allowing external AI agents to control Bitwig Studio through text-based commands.

how to use WigAI?

To use WigAI, install the extension in Bitwig Studio, activate it in preferences, and connect an external AI agent to the MCP server at http://localhost:61169/mcp to send commands.

key features of WigAI?

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

use cases of WigAI?

  1. Hands-free control of music production in Bitwig Studio.
  2. Integration with AI assistants for automated music workflows.
  3. Enhancing creative processes with AI-driven commands.

FAQ from WigAI?

  • What is required to use WigAI?

You need Bitwig Studio (5.2.7 or later), Java 21 LTS, and an external AI agent that supports the Model Context Protocol.

  • How do I install WigAI?

Copy the WigAI.bwextension file to your Bitwig Studio extensions directory and activate it in preferences.

  • Can I use any AI agent with WigAI?

Yes, as long as the AI agent supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fabb
Star
2
Language
Java
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago