openDAW MCP

What this does

openDAW MCP exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:

OPENDAW_HOST_DIR
OPENDAW_URL
OPENDAW_EXPORT_DIR
NODE_BIN_DIR

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install openDAW MCP?

The install section on this page carries the maker's install command for openDAW MCP, as submitted. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with openDAW MCP?

This page carries setup and config for Claude Code. Any other MCP client that accepts a standard server config can connect to openDAW MCP as well.

Does openDAW MCP need an API key?

This listing does not flag an API key as required. The server can use these environment variables: OPENDAW_HOST_DIR, OPENDAW_URL, OPENDAW_EXPORT_DIR, NODE_BIN_DIR; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.