opendaw-mcp
PulseGate's liveness check found it on 14 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 4 Jul 2026. How this is checked
opendaw-mcp is an open-source Python package offering 250 Model Context Protocol (MCP) tools for agent-native control of openDAW, a browser-based digital audio workstation. It enables developers to automate and extend music production workflows using agents and scripting. Ideal for those building advanced audio and music automation solutions.
Inferred · not functionally tested
Overview
6 featuresPurpose: Enabling agent-based automation and control of openDAW for music production workflows.
Inferred · not functionally tested
Audience: developers building agent-native music production tools
Inferred · not functionally tested
Functions: agents, workflow_automation
Inferred · not functionally tested
Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI · deployment: cli
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
In the Frameworks & runtimes space, opendaw-mcp takes a focused approach. Inferred · not functionally tested: It focuses on enabling agent-based automation and control of openDAW for music production workflows. Inferred · not functionally tested: opendaw-mcp is an open-source project aimed at developers building agent-native music production tools. Basis unknown · not verified: opendaw-mcp is open source under the Apache-2.0 license. Basis unknown · not verified: It ships for the command line.
It is developed by AMEOBIUS, and it first shipped in 2026. Development happens publicly on GitHub with 147 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are MCP tools, agent-native control, and DAW integration. Basis unknown · not verified: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- MCP tools
- Agent-native control
- DAW integration
- Music production
- Audio synthesis
- MIDI support
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
What PulseGate has recorded for this listing
Frequently asked questions about opendaw-mcp
- What does opendaw-mcp do?
- Inferred · not functionally tested: Opendaw-mcp focuses on enabling agent-based automation and control of openDAW for music production workflows. It is catalogued under Frameworks & runtimes on PulseGate.
- Who is opendaw-mcp for?
- Inferred · not functionally tested: opendaw-mcp is an open-source project built for developers building agent-native music production tools.
- Does opendaw-mcp have a free plan?
- Basis unknown · not verified: Yes — opendaw-mcp is open source under the Apache-2.0 license and free to use.
- What platforms does opendaw-mcp run on?
- Basis unknown · not verified: opendaw-mcp runs on the command line.
- Is opendaw-mcp still maintained?
- PulseGate's liveness check found it on 14 Sep 2026. Its GitHub repository shows 147 commits in the last 90 days.
- What projects are similar to opendaw-mcp?
- Similar projects tracked by PulseGate include slack_connect, ship-on-friday, and send-that-email.slack_connectship-on-fridaysend-that-email
- Who develops opendaw-mcp?
- opendaw-mcp is developed by AMEOBIUS.
- When did opendaw-mcp launch?
- opendaw-mcp first shipped in 2026.
Also in Frameworks & runtimes
Same category — not a similarity match