play_note
Play a single test note (quick sanity check). Not for full DJ segments—use queue_segment for those.
LABSCO SUMMARY
Built for a set that keeps playing while the next section is still being written.
The tool descriptions steer you toward queue_segment for anything long and warn against ad-hoc snippets, with run_code kept as its compatibility alias and play_note reduced to a sanity check. stop_all is the emergency exit and the descriptions say so — it kills every running job rather than fading out. Nothing reads back what is currently playing, so the session state stays in Sonic Pi.
What it is
A bridge to a live Sonic Pi session runner: code goes over OSC to a session that is already playing.
What you get
- Queued musical segments handed to the session runner for crossfaded transitions
- A single test note with the synth, sustain and cutoff chosen in the call
- A hard stop that ends every running Sonic Pi job at once
Requirements
Sonic Pi installed and running, with the v2 DJ session runner listening for OSC — every call is sent into that session rather than rendered on its own.
Setup effort
One command — npx -y sonic-pi-mcp
USE CASES
01
Keeping a set playing while the next section is still being written
Queue each segment into the running session so transitions crossfade instead of restarting, and keep the hard stop for when something has gone wrong rather than for musical endings.
02
Checking the synth is actually audible before a set starts
One note with a chosen synth, sustain and cutoff tells you the session runner is listening and the audio path works.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
queue_segment
Push the next music segment to Sonic Pi. Use with the v2 DJ session runner for crossfaded handoffs. Prefer this over ad-hoc snippets for long sets.
run_code
Alias of queue_segment for compatibility. Sends Sonic Pi code over OSC to the session runner.
stop_all
Hard stop: stop all running Sonic Pi jobs (like the Stop button). Use sparingly; prefer queue_segment for musical transitions.
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"sonic-pi-mcp": {
"command": "npx",
"args": [
"-y",
"sonic-pi-mcp"
]
}
}
}npx
TERMINAL
npx -y sonic-pi-mcp
