Audionaut MCP
The MCP server of the Audionaut editor: an agent cuts, moves, fades, analyses and exports multitrack audio projects.
- 271 ★ on the repository
- Last commit
Extended access
Why this level
- Changes project files and exports audio to disk; in an open project edits go into the undo history.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/audionaut-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Changes project files and exports audio to disk; in an open project edits go into the undo history.
This is third-party code. Review the repository files before installing.
What it does
Audionaut is a free open-source multitrack audio editor for music, podcasts and recordings. The `audionaut-mcp` package lets agents in Claude Code, Claude Desktop and other clients drive Audionaut projects: cut and move clips, apply fades and crossfades, analyse segment boundaries, tempo and onsets, run auto-edit, separate tracks into stems and export the result. The package is only a wrapper: each tool runs one `audionaut-cli` command with the `--json` flag and relays the answer. If the project is open in the app, the command goes to the app and each edit becomes one step in the undo history, with the user's unsaved changes taken into account.
Who it is for. Musicians and podcast editors who edit audio in Audionaut and want to hand routine work to an agent: slicing, fades and export.
Good fit when
- A song has to be sliced every 16 bars and clips spread across two tracks.
- After editing, the agent sets crossfades and a fade-out at the end.
- Tempo and segment boundaries of a track are needed before work starts.
- A recording is separated into stems and the result is exported as a separate file.
Not a fit when
- The Audionaut app is not installed, and the package does nothing on its own.
- You need hands-on editing by ear with instant response, while the agent works through commands.
- On macOS the projects are outside the Music folder, which the sandbox does not allow.
Example request
Split the clip in the Demo Project.audium project every 16 bars, spread the parts across two tracks and add a fade-out at the end.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
AUDIONAUT_CLI- Path to the app or `audionaut-cli` if the server did not find them.
Limitations
It needs the Audionaut app (1.6.3 or newer recommended) and Node.js 18 or newer. On macOS the app is sandboxed and sees only the `~/Music` folder, so projects, audio to import and export targets have to sit there or the server answers `sandbox_denied`. For `separate_stems` the Demucs model is downloaded once in the app, and its weights are licensed for research use. Stem separation and exporting a long project take minutes.
How to disable. Remove the audionaut entry from the MCP configuration (`claude mcp remove audionaut`). Projects and the Audionaut app stay in place, and the `audionaut-mcp` package is fetched through `npx` and stores nothing.
FAQ
How do I connect Audionaut to Claude Code?
Install the Audionaut app and run `claude mcp add audionaut -- npx -y audionaut-mcp`. For Claude Desktop add an entry with the command `npx` and the arguments `-y audionaut-mcp` to `claude_desktop_config.json`.
What happens if the project is open in the app?
The command goes to the app and the edit lands in the undo history as one step. Saving stays with the user and `Project.json` is not touched.
How do I check that the server found the app?
Run `npx -y audionaut-mcp --check`. The server looks for the app through `AUDIONAUT_CLI`, then a built `audionaut-cli`, then `PATH` and the standard install locations.
Why does it answer `sandbox_denied`?
On macOS the app sees only `~/Music`. Move the project and audio into that folder, for example `~/Music/Audionaut`.
How long does stem separation take?
Minutes for a full song. If the client sends a `progressToken`, `separate_stems`, `export_audio` and `analyze` report progress, and a call stops only after ten minutes with no sign of life.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for Audacity 3.x with 144 tools and 9 pipelines for audio cleanup, mastering and transcription, all processed locally.
The audio package runs an MCP server for sound work: loudness, spec checks, denoise, EQ, cuts and tempo.
MCP server and panel let an agent read an Adobe After Effects comp and build animation as ordinary editable layers and keyframes.
An MCP server with 59 tools for CapCut and OpenCut editing: tracks, clips, text, transitions and voiceover from Cursor and Codex.
An MCP server for Ableton Live: the agent creates tracks, places clips and builds arrangements straight in the open project
A local MCP server generates music and sound effects, builds loops, adjusts loudness and exports audio for games or video.
README in short
The server lives in the `Tools/audionaut-mcp` folder of the editor repository and is published in the MCP registry. Details for agents are in chapter 11 of the user manual.