About openDAW MCP
262 MCP tools for agent-native control of openDAW, a browser-based DAW
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
docker run -i --rm -e OPENDAW_HOST_DIR -e OPENDAW_URL -e OPENDAW_EXPORT_DIR -e NODE_BIN_DIR ghcr.io/ameobius/opendaw-mcp:1.13.0OPENDAW_HOST_DIRPath to the headless openDAW host directoryOPENDAW_URLURL of the running openDAW Vite dev serverOPENDAW_EXPORT_DIRDirectory for rendered audio exportsNODE_BIN_DIRPath to Node.js binary directory (if not on PATH)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
ghcr.io/ameobius/opendaw-mcp:1.13.0stdioTools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
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.