monody
Menu
Download

A DAW you can drive from Claude Code, over MCP

Use Claude Code to read and edit a monody session. Lifetime, Pro and Studio include MCP access; you provide your own Claude Code access.

Download monody

Before you connect

monody is available for Windows and macOS. These connection steps were checked against the Mac release with Claude Code on the same computer. Sign in to monody with an account that has MCP access. The public Lifetime, Pro and Studio plans include it; your Claude Code access is separate.

To try the editor first, download monody. Free local editing and export support up to eight tracks and need no account or AI credits. You can try that part of the app before choosing an MCP plan.

How it connects

monody's MCP server runs inside its desktop app. Claude Code connects to that app and works on the project you have open.

  • The server runs inside the monody app, at http://127.0.0.1:<port>/mcp (streamable HTTP, protocol 2025-06-18).
  • It listens only on your machine, and it needs a key that monody creates for you.
  • Settings → Account → Use monody from Claude shows the line to paste. It looks like this:
claude mcp add --transport http monody http://127.0.0.1:8710/mcp \
  --header "Authorization: Bearer <your key>"

Copy it from the app: the port and key are yours. Keep monody open on the same computer.

Run the copied command in the terminal folder where you will use Claude Code, then start claude from that folder. The command uses Claude Code’s default local scope, so monody will not automatically appear in other projects. Use /mcp inside Claude Code to check the connection. An “Added” message means the configuration was saved; it does not prove a working connection. See Claude Code’s MCP setup guide.

Keep the copied command private. New key disconnects clients using the old key until you update their connection settings; it is not needed for routine connection checks.

The tools

Tool What it does
get_project Reads the whole session: tempo, tracks, clips, notes, device chains, automation, routing, transport, and the schema of every device
run_commands Applies a batch of monody commands as one labeled, undoable transaction; all or nothing
transport Play, stop, seek, set the loop
apply_sound_preset Puts one of monody's preset sounds (or a random one) on a MIDI track
undo / redo Steps through history, yours and the AI's
render_wav Renders the song to a WAV file
analyze_mix Renders the song and measures it for release: LUFS, true peak, balance, masking, sections
master_to_target Adjusts loudness toward a target as one undoable step and reports the measured result; on Mac since 0.9.3, mode: "tonal" can also add one gentle EQ (at most 3 dB)
separate_stems On Mac since 0.9.3: separates one audio clip into vocals, drums, bass and other, then adds the parts you choose as new tracks in one undoable step. The separation model is installed from the app; the result is an estimate

The result may miss the target. Read the measured LUFS and true peak, then listen before keeping the change or exporting. The server lists more tools than this table, for example for the sound library and plugins; your client's tool list shows the full set.

The command vocabulary ships with the server as MCP instructions, and get_project returns the schema of every device, so the model knows the commands and the parameters before it changes anything.

Why a DAW behind the commands matters

  • It's a real session. Arrangement, piano roll, a deep synth, about 50 effects, mixer, automation, recording and stems. Everything the AI does, you can also do by hand, and see.
  • Edits are checked. Commands are validated before anything changes. A bad payload comes back as a structured error, not a half-applied edit.
  • Undo is exact. Each call is one step in the app's history, labeled and attributed to the AI.
  • The engine is deterministic. Offline renders are bit-exact, and the test suite checks them against a golden render.

Try one change first

Open a project with a part you can already hear. In the project menu, choose Save a copy…, give it a clear name, then Save and open copy. Check that the copy is open before asking Claude to edit it. Opening a copy resets ordinary Undo/Redo; your original remains available in Projects.

First ask:

Read the current project without changing anything. Tell me its name, the track names and their current volume settings, and which tracks have volume automation. Then wait.

Check the answer against monody. Pick one uniquely named, audible track without volume automation and replace [track name] below:

Read the project again, then lower only “[track name]” by 3 dB in a single run_commands call. If the name is ambiguous, its volume is automated, or the change is refused, stop and explain. Leave everything else as it is. Report the confirmed before and after values, then wait.

Check the named track and its value in monody, then listen. Keep the change if it helps. To undo this one confirmed edit, use ⌘Z in monody before making another edit or switching projects. One successful run_commands call is one Undo step; a request spanning several calls may need several steps. If the result is unclear or a connection drops, read the project before trying again.

More requests to try

Once the connection and a small edit work, try another specific task:

  • "Route the drums to a new bus and put a bus compressor on it."
  • "Add a tempo-synced delay to the lead, dotted eighth, mostly dry."
  • "Sit the hats back 3 dB and pan them a little left."
  • "Analyze the mix for streaming and tell me the three biggest problems."

Looking for Ableton Live or another DAW?

This page is about monody's own built-in MCP server. If you want Claude to edit a running Ableton Live set, that takes a different setup, covered in Ableton MCP: every way to let an AI edit your Live set. For REAPER, which is scripted through ReaScript and several community bridges, see REAPER and AI, and for Bitwig's controller extensions, Bitwig and AI. For what Claude can do across DAWs today, see Claude for music production. MCP access is part of the Lifetime, Pro and Studio plans.

Limits

For musical prompts and the different connection options, see ChatGPT for music production. That guide distinguishes documentation from integrations we have tested.

  • These setup steps cover the public Mac app. The MCP connection on Windows is outside this guide’s verification.
  • The server listens on your computer’s loopback address. A client on another machine cannot connect directly. Some services offer a private connection option, such as OpenAI's Secure MCP Tunnel, but that requires additional setup and compatible authentication. We have not tested that route with monody.

Finish wording was reviewed against public v0.9.0 source on 9 October 2026. Connection and first-edit instructions were reviewed against public Mac 0.9.2 source and Claude Code’s MCP documentation on 12 October 2026 (13 October UTC). The tool table was checked against the 0.9.3 Mac source on 16 October 2026. These were source reviews, not a new connection, assistant session or listening test.

Questions

Do I need to install a plugin or a remote script?
No. monody serves MCP itself, over streamable HTTP on your own machine (127.0.0.1). You add it to your MCP client with one command, which monody shows you in Settings → Account.
Which plan includes MCP?
Lifetime, Pro and Studio include MCP access; you provide your own client and model access. Free includes local editing and export with up to eight tracks, plus a monthly credit allowance for the separate built-in assistant. It does not include external MCP access.
Does using monody from Claude Code spend monody's AI credits?
No. Claude Code uses your own model access. monody carries out the tool calls and renders audio on your computer; those MCP calls do not spend monody's AI credits.
Can the AI break my project?
Every run_commands call is one transaction. If any command in it fails validation, nothing is applied and the error comes back for the model to fix. Each successful call is a single labeled undo step, so ⌘Z in the app walks back exactly what it did.
Does it work with clients other than Claude Code?
Claude Code is the client we test with. Another client needs to reach monody's local streamable-HTTP server and send its bearer header. A web client cannot reach that localhost address directly; an additional connection, such as a compatible tunnel, would be needed. We have not verified a web-client connection to monody.