openDAW MCP

io.github.AMEOBIUSPublished by GitHub account AMEOBIUSv1.13.0Updated Oct 27, 2026

262 MCP tools for agent-native control of openDAW, a browser-based DAW

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

Gives an assistant 262 MCP tools to control openDAW, a browser-based digital audio workstation, from a local process.

What you can do
  • Control openDAW project and arrangement state through a large tool set aimed at agent-driven music production
  • Operate the browser-based DAW running on a local Vite dev server, with a headless host directory
  • Render and export audio into a configured export directory
  • Run as a local stdio process, typically from a container image, on a desktop machine
When to use it
Useful when you want an AI assistant to drive openDAW sessions programmatically, for example to build or modify arrangements and render audio, and you already run openDAW locally.
Requirements
A local desktop machine; the container image ghcr.io/ameobius/opendaw-mcp:1.13.0 over stdio. Requires OPENDAW_HOST_DIR (headless openDAW host directory) and OPENDAW_URL (URL of a running openDAW Vite dev server). Optional NODE_BIN_DIR if Node.js is not on PATH, and OPENDAW_EXPORT_DIR for rendered audio exports.
Before you install
It drives a running DAW instance and can render and write audio files to the export directory, so changes to projects and files should be reviewed. It needs a reachable local dev server URL and host directory path, which exposes local paths to the server process. No authentication is declared.

Installation

In SourceWeft

  1. Open openDAW MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.13.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.