Control dew from an agent
dew runs a Model Context Protocol server inside the application, so a coding agent can read and change the project you have open: instruments, effects, the mixer, the notes and the arrangement.
How it works
Turn it on under Audio → MCP. dew listens on the loopback interface only. The first time a client connects, dew asks whether to allow it, and whether it may only read or change things too. Every change it makes is one step of your undo history.
Connecting a client
The MCP settings panel shows the address and the exact command. The port is not fixed, so copy the command rather than typing it.
What it can reach
One address space covers every value in the document. A target, an id, a group and a slot name any parameter of any oscillator, envelope, sample, soundfont, effect, mixer insert or the master. The same four fields say what a curve can be pointed at.
Writing a score
For anything longer than a few bars, an agent writes dew’s arrangement language and compiles it, which takes one call rather than one per note.
Resources
dew serves these as MCP resources. A client should read the first before its first call.
- Driving dew — What dew is, and which tool answers which question.
- How things are addressed — Ids, indexes, and the five fields that name any parameter.
- Notes, patterns and the arrangement — Steps and bars, and why a pattern is not an instrument.
- The score language — When to write music as text instead of as notes.
- Changes, undo and consent — What a grant covers, and what protects the user.