Ardour MCP Server

Ardour MCP server exists for a simple reason — assistants are far more useful when they can act on Ardour directly instead of describing what you should do. mcp server to connect Ardour 9 DAW.

What you get

ardour_mcp_server is a server that implements the Model Context Protocol (MCP) to provide an interface for controlling Ardour (a digital audio workstation) via Open Sound Control (OSC) messages. It allows external applications or scripts to interact with Ardour, automating tasks, and extending its functionality.

• Control Ardour transport (play, stop, locate, speed, etc.)
• Manage tracks (mute, solo, record enable, gain, trim)
• Execute general Ardour menu actions via /ardour/access_action
• Read Ardour state (e.g., playback state)
• MCP-compliant interface for easy integration

What the assistant can call

Once Ardour is connected, these are the calls the assistant has available:

• Overview — ardour_mcp_server is a server that implements the Model Context Protocol (MCP) to provide an interface for controlling Ardour (a digital audio
• Features — The Features tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

• Rust: Ensure you have Rust installed. You can get it from rust-lang.org. * Ardour: A running instance of Ardour 6.x, 7.x, 8.x or 9.x. * Ardour OSC Configuration: * In Ardour, go to Edit > Preferences > Control Surfaces. * Enable "OSC". * Ensure the "Listen Port (UDP)" is set to 3819 (or update the server configuration if you use a different port). *

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ardour's toolset — Overview, Features, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by pyroqbit; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ardour mcp server does with a few real requests.