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

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. Or use a DAW that is its own MCP server, like monody.

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.

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 server for a DAW turns tool calls into actions in that DAW. Because most DAWs have no public API for this, each server finds its own way in, and that way in sets its limits.

ChatForest's roundup also lists servers for Cubase that work over MIDI, and notes that it found none for Studio One. These are all community projects, not made by the DAW companies (the Pro Tools server uses Avid's official scripting API, but it's still a community project).

Things to know before you connect one:

• You need a desktop client. Claude Desktop, Claude Code, Cursor and similar apps can run or reach servers on your computer. The Claude website can't.
• Undo varies. Some servers turn each edit into one undo step in the DAW; some warn that their edits can't be undone. Save a copy of your project first.
• Approve tool calls at first. Claude Desktop asks before each tool call by default. Watch what each one does before you let it run freely.

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 for macOS: arrangement, piano roll, a deep synth, about 50 effects, mixer, automation, recording and stems.

To connect Claude Code:

1. Open monody → Settings → Account → Use monody from Claude.
2. Copy the command shown there. It looks like this, with your own port and key:

claude mcp add --transport http monody http://127.0.0.1:8710/mcp \
  --header "Authorization: Bearer <your key>"

3. Run it in a terminal, then ask Claude Code for something in plain words.

What Claude gets:

• get_project reads the whole session: tempo, tracks, clips, notes, device chains, automation and routing, plus the schema of every device.
• run_commands applies a batch of monody's own commands as one labeled, undoable transaction. If any command fails, nothing is applied and the error goes back to Claude to fix.
• transport, undo / redo, apply_sound_preset and render_wav, plus analyze_mix (measures the song for release) and master_to_target (lands it on a loudness target in one undoable step).

MCP access comes with monody's Pro and Studio plans. The model runs in your client on your own Claude plan, so it doesn't use monody's AI credits. The server only listens on your own machine. More on the MCP page.

Good first requests

Start with chores you can check at a glance, in any DAW:

• "Route the drums to a new bus and put a compressor on it."
• "Sit the hats back 3 dB and pan them a little left."
• "Add a tempo-synced delay to the lead, dotted eighth, mostly dry."
• "Rename and color the tracks by instrument."
• "List every track with its devices and their main settings."

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. Requests you can check are where Claude saves you time, and they keep the track yours.

Sources

• Anthropic: Claude for creative work (28 April 2026)
• GitHub: ahujasid/ableton-mcp, bonfire-systems/reaper-mcp, WeModulate/bitwig-mcp-server, koltyj/logic-pro-mcp, skrul/protools-mcp-server, calvinw/fl-studio-mcp, AgriciDaniel/claude-music, bitwize-music-studio/claude-ai-music-skills
• ChatForest: Music and audio production MCP servers
• Model Context Protocol: Connect to local MCP servers; Claude Code: MCP

Checked on 1 October 2026. 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.