monody
Menu
Download

Claude for music production: what it can do in a DAW today

What Claude can do in music production: advice in chat, documentation connectors and MCP edits in a DAW, with setup requirements and limits.

The short answer. In a plain chat, Claude can explain, suggest and write notes out as text, but it can't see your session. Anthropic's Ableton connector answers from Ableton's documentation; it doesn't control Live. To let Claude edit a session you need an MCP server for your DAW: community ones exist for Ableton Live, REAPER, Bitwig, Logic Pro, Pro Tools and FL Studio, each limited by how it gets into the DAW. monody has an MCP server built in. Ardour also documents an experimental MCP HTTP surface.

People search "Claude for music production" hoping for very different things: help with theory, a finished song, or an assistant that changes their actual project. Those are three different setups. Here's what each one does today, with sources.

If you already have a connected DAW, skip to a first request you can check. In monody on Mac, try turning one track down by 3 dB on a saved copy. Play the same bars and decide whether to keep the change. You'll need your own Claude Code access and a monody license that includes MCP: Lifetime, Pro or Studio.

In a plain chat: no tools

With no tools connected, Claude works from what you type or paste. That's still useful:

  • explaining theory: why a borrowed chord works, what a Dorian bassline is, how a build creates tension
  • talking through a mix problem you describe ("the kick disappears when the bass comes in")
  • writing parts out as text: note names, a drum grid, or a list of pitches, start times and lengths
  • writing code that writes a .mid file, which you then drag into your DAW (Claude Code can run that code for you)

What it can't do in a plain chat is look at your session. Anything it says about your track is based on your description.

Anthropic's music connectors

On 28 April 2026 Anthropic announced connectors for creative tools. Two matter for producers:

  • Ableton: "Ableton grounds Claude's answers in official product documentation for Live and Push."
  • Splice: "Splice gives music producers the ability to search its catalog of royalty-free samples from within Claude."

So Claude can answer "how do I set up a sidechain in Live?" from Ableton's manual and find samples on Splice. Neither connector opens your project or changes it.

MCP servers for DAWs

MCP (the Model Context Protocol) is how Claude calls outside tools. A DAW server exposes particular operations through a script, extension, API or UI control. Those operations determine what you can ask it to do.

Source review, 8 October 2026. We read the repositories below; we did not install these servers or test them in a DAW. Every row describes the maintainer’s documented scope, not a compatibility or music-quality result. Dates link to the latest default-branch commit observed that day, not a package release or a successful test. Server names link to the README version reviewed.

DAW / server Connection Documented access and limits Commit / license
Ableton Live: ahujasid/ableton-mcp Python server and a Remote Script inside Live. Tracks, MIDI clips, devices, transport and arrangement edits. Designed around Live’s built-in devices and browser items; larger requests may need smaller steps. 2026-09-22; MIT
Ableton Live: Pantani/ableton-mind Node.js server and a Python Remote Script over TCP. Live object access, device parameters, recipes and automation. The maintainer labels it alpha with an unstable API and advises against production use; deeper Max for Live control is still pending. 2026-06-24; MIT
Ableton Live + Bitwig: ptaczek/daw-mcp Node.js bridge; Ableton Remote Script or Bitwig Java extension. Reads and writes MIDI clips in Session View or the Clip Launcher. No Arrangement View, audio clips, automation or mixing; it does not listen live. 2026-01-01; MIT
REAPER: bonfire-systems/reaper-mcp Python server using python-reapy’s distant API. Project, track, MIDI, FX, routing, rendering and analysis tools. Requires REAPER 7+ running with its distant API enabled. 2026-10-07; MIT
REAPER: TwelveTake-Studios/reaper-mcp Python server exchanges local files with a Lua bridge running in REAPER. Track, MIDI, FX, routing, automation, render and measurement tools. The supplied JSFX analyzer is needed for true-peak, spectrum and stereo measurements. A long render can outlast the request timeout while REAPER continues. 2026-09-29; MIT
Bitwig Studio: WeModulate/bitwig-mcp-server Python server sends OSC through Driven by Moss; Bitwig 5.2+. Transport, levels, pan, mute, device parameters and project information. The maintainer warns that documentation and implementation may disagree. 2025-04-10; MIT
Bitwig Studio: fabb/WigAI MCP server inside a Bitwig controller extension; Bitwig 5.2.7+ and Java 21. Transport, selected-device parameters, clip and scene launching. Requires building and activating the extension; the README does not document whole-project MIDI editing. 2026-04-17; README says MIT; linked license file missing
Logic Pro: koltyj/logic-pro-mcp CoreMIDI, Accessibility, keyboard events, AppleScript and OSC on macOS. Transport, tracks, mixer actions and MIDI messages. Region MIDI data and automation curves are unavailable through Accessibility; plug-in control depends on visible UI. Requires Accessibility and Automation permissions. 2026-09-05; MIT
Pro Tools: skrul/protools-mcp-server Node.js server uses Avid’s PTSL API; Pro Tools 2024.10+ and a matching SDK file. Session queries, audio-clip navigation, transport and editing. MIDI timeline positions cannot be indexed. Write groups require enabling; the default still allows playback, mute/solo and temporary audio exports. 2026-01-26; MIT
FL Studio: calvinw/fl-studio-mcp Python server queues notes; a keystroke triggers a piano-roll script. Reads, adds, replaces and deletes piano-roll notes. Manual edits need a state refresh. macOS needs Accessibility permission; Windows support is partial. 2025-12-14; MIT

For more context on the different approaches, see Ableton MCP, REAPER and AI, Bitwig and AI, Cubase AI features and Pro Tools and AI. These bridges are community projects. Using an official API, as the Pro Tools bridge does, does not make a server an official DAW integration.

Ardour's official manual also describes an experimental MCP HTTP control surface, including session inspection, track and plugin changes, and MIDI editing. This is separate from community OSC bridges. Check whether your installed Ardour build provides MCPHttp under Preferences, Control Surfaces. We reviewed the documentation on 13 October 2026; we have not tested that build or a Claude connection.

We also checked opendaw-mcp on PyPI. Its listed GitHub repository returned 404 on 8 October, so we could not verify a current commit and have left it out of the comparison. That does not establish whether an already downloaded package works.

Things to know before you connect one:

  • Match the client to the connection. Use a local MCP client for a server running only on your computer. Claude's web app supports remote connectors, whose requests come from Anthropic's cloud. The server must be reachable from there; a localhost address alone won't work. We haven't tested these DAW servers through a remote connector.
  • Check what leaves your computer. A local bridge does not mean a local model. Review your client's data settings and the server's own collection policy. For example, ahujasid/ableton-mcp documents default-on anonymous usage telemetry and separate, opt-in recording of project content for a dataset; see its linked README.
  • Save a copy before editing. Check the server's undo behavior on a disposable project. A tool-call timeout does not always mean that the DAW stopped the operation.
  • Review the available tools first. Begin with a read operation, then approve one small edit whose result you can see. A MIDI-only bridge cannot carry out a mixing request.

Claude Code skills that make songs

A different branch: Claude Code skills that make finished audio or plan it for an audio model.

  • claude-music is a Claude Code skill that makes full songs with vocals from text descriptions, using the open-source ACE-Step 1.5 model on your own NVIDIA GPU.
  • claude-ai-music-skills is a set of 53 Claude Code skills for concept, lyrics, Suno prompts, mastering and release prep; the audio itself is made on Suno.

They answer a different question from DAW servers. A DAW server changes the project you're working on. These produce audio, or prompts for a model that produces audio.

A DAW with its own MCP server: monody

monody, the DAW we make, has the MCP server built into the app, so there's no script or extension to install in another program. It's a desktop DAW: arrangement, piano roll, a deep synth, about 50 effects, mixer, automation, recording and stems.

monody is available for Windows and macOS. To connect Claude Code on Mac, sign in and use the command in Settings → Account → Use monody from Claude. The Lifetime license includes MCP for a one-time $149 purchase. It keeps the Free plan's 50 monthly credits for the built-in assistant. Pro and Studio subscriptions include MCP and larger monthly assistant allowances.

Once connected, Claude can read the session and change notes, devices or routing. A batch of monody commands is one labeled Undo step. If a command in the batch fails validation, nothing in that batch is applied. Other tools can render audio and measure the mix against a release target. On Mac, tonal mastering and audio stem separation have been available since 0.9.3; separation needs a model you install in the app.

You provide your own Claude Code access; MCP calls do not spend monody's AI credits. monody executes the tool calls on your computer, and its MCP server listens only on that machine. The MCP page has the setup command, the full tool list and a first read, one edit and Undo exercise to try on a saved copy.

Good first requests

First check the connected server’s tools. Ask it to list the tracks or read the selected MIDI clip, whichever it supports. After saving a copy, choose one small edit from its documented scope. For a bridge with mixer and device access, examples include:

  • "List every track with its devices and their main settings without changing anything."
  • After checking the read-only result, follow the single-track level exercise.

Once that small edit and its undo work, try a more involved request:

  • "Route the drums to a new bus and put a compressor on it."
  • "Add a tempo-synced delay to the lead, dotted eighth, mostly dry."
  • "Rename and color the tracks by instrument."

In monody you can also ask for a release check: "Analyze the mix for streaming and tell me the three biggest problems." The loudness numbers behind that are in How loud should your master be?.

Leave "write my song" for last. Start with a request whose result you can inspect and hear before asking for the next change.

Sources

DAW server documentation, repository metadata and Claude's local/remote connection requirements checked on 8 October 2026. The creative-connector and music-skill sections retain their 1 October review; no DAW runtime test was performed for this update. Ableton, Live and Push are trademarks of Ableton AG. monody is not affiliated with or endorsed by Ableton, Anthropic or the DAW makers named here.

The monody tool descriptions are based on the 16 October review of the 0.9.3 Mac source. Plan details and the first-task link were checked against monody's pricing and MCP pages on 5 November 2026. No new MCP connection or listening test was performed.

Questions

Can Claude make music?
In a plain chat Claude works in text. It can explain theory, suggest progressions and write notes out as text or as code that writes a MIDI file. Making audio takes another tool, such as a Claude Code skill that drives an audio model. Editing a session in your DAW takes an MCP server for that DAW.
Can Claude control my DAW?
Yes, through MCP servers. Community servers exist for Ableton Live, REAPER, Bitwig Studio, Logic Pro, Pro Tools and FL Studio, and they differ a lot in what they can reach. monody, a separate DAW, has an MCP server built in. Ardour also documents an experimental built-in MCP HTTP surface.
Does Anthropic's Ableton connector let Claude control Ableton Live?
No. Anthropic says it "grounds Claude's answers in official product documentation for Live and Push". It answers questions about Live; it doesn't open or edit your set.
What do I need to connect Claude to a DAW?
For a local setup, use a client such as Claude Desktop or Claude Code, an MCP server for your DAW, and any script, extension or device it needs. Claude's web app supports remote MCP connectors, but cannot directly reach a server available only on your computer's localhost.
What should I ask Claude to do in a DAW first?
First ask what the connected server can read and change. Start by listing tracks or reading a MIDI clip, if supported, then make one small edit on a saved copy. Mixing, routing and device requests only work through servers that expose those operations.