abhishekjairath/sonic-pi-mcp

Model Context Protocol (MCP) server for Sonic Pi. Describe music in natural language in your LLM client; the model generates Sonic Pi code and this server sends it over OSC. Use the included queue runner in Sonic Pi for crossfades between segments.
## Features
queuesegment — send the next full musical segment (named liveloops, usebpm, etc.).
runcode — same as queuesegment (compatibility).
stopall — hard stop via OSC (/stop-all-jobs), like Sonic Pi’s Stop.
playnote — quick test note.
Resource — DJ session craft, vocabulary, and tool usage (read from the MCP client).
Prompt nextperformancesegment — help frame the next block for longer sets.
Env — OSCHOST, OSCPORT, OSCCODEPATH, OSCSTOPALLPATH.
## Prerequisites
Sonic Pi v4.x
Node.js 18+ (npx / node)
An MCP-capable client (Cursor, Claude Desktop, VS Code with MCP, etc.)
Optional: Bun for local development (bun run dev).
## One-time Sonic Pi setup (queue runner)
1. Open Sonic Pi.
2. Copy sonic-pi-queue.rb into a buffer.
3. Press Run and leave it running.
The buffer listens on the default OSC port and crossfades between segments sent by the MCP.
## Install the MCP server
bash
npx -y sonic-pi-mcp
Point your client at this command over stdio (see below).
### Cursor
Use ~/.cursor/mcp.json and/or .cursor/mcp.json in a project:
json
"mcpServers": {
"sonicpimcp": {
"command": "npx",
"args": ["-y", "sonic-pi-mcp"]
Local clone (after npm install or bun install and bun run build):
json
"mcpServers": {
"sonicpimcp": {
"command": "node",
"args": ["/absolute/path/to/sonic-pi-mcp/bin/cli.mjs"]
Bun without building — some clients ignore cwd; use an absolute path to src/server.ts, or use the launcher:
json
"mcpServers": {
"sonicpimcp": {
"command": "/absolute/path/to/sonic-pi-mcp/bin/mcp-dev.sh",
"args": []
Run chmod +x bin/mcp-dev.sh once. The script changes into the repo and runs bun run src/server.ts.
### Claude Desktop
~/Library/Application Support/Claude/claudedesktopconfig.json (paths differ on Windows):
json
"mcpServers": {
"sonicpimcp": {
"command": "npx",
"args": ["-y", "sonic-pi-mcp"]
For a local clone, prefer bin/mcp-dev.sh (see above) if you see Module not found "src/server.ts" or spawn bunx ENOENT. Remove and re-add the MCP in the app if an old definition is cached.
### VS Code
Configure your MCP extension to run npx with -y and sonic-pi-mcp, stdio transport, per the extension’s docs.
## Environment variables
| Variable | Default | Meaning |
| OSCHOST | 127.0.0.1 | Sonic Pi host |
| OSCPORT | 4560 | Sonic Pi OSC port |
| OSCCODEPATH | /run-code | OSC path for code (must match your Sonic Pi buffer) |
| OSCSTOPALLPATH | /stop-all-jobs | Hard stop path |
Allow incoming OSC in Sonic Pi if you connect from another machine; set OSCHOST accordingly.
## Development
bash
git clone https://github.com/abhishekjairath/sonic-pi-mcp.git
cd sonic-pi-mcp
bun install # or npm install