Control Ardour through its built-in MCP HTTP control surface or its native OSC interface. For Codex, 1 route is explicitly documented by the integration maintainer.
Ardour’s OSC interface exposes control-surface operations to external applications.
Platforms: Windows, macOS, Linux
The native interface is documented, but no setup for this coding agent is established by this source.
Ardour with OSC enabled and a compatible client configured for the session.
OSC control requires an external client or bridge; it does not provide automatic coding-agent setup.
Ardour includes an MCP HTTP control surface for session and audio-production workflows.
Platforms: Windows, macOS, Linux
The maintainer documents Codex setup for this connection.
An Ardour build with MCPHttp support, enabled in Preferences → Control Surfaces; configure the local HTTP endpoint.
The manual describes the interface as experimental. It uses HTTP rather than SSE and some region targeting is unavailable.
| Integration | Codex compatibility | Requirements |
|---|---|---|
| Ardour OSC | Not documented | Ardour with OSC enabled and a compatible client configured for the session. |
| Ardour MCP HTTP | Documented setup Setup guide | An Ardour build with MCPHttp support, enabled in Preferences → Control Surfaces; configure the local HTTP endpoint. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Codex and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Ardour integrations