This MCP server allows AI assistants to interact with Sonic Pi through OSC messages, enabling AI tools like Claude and Cursor to create music and control Sonic Pi programmatically. You can play individual notes with customizable parameters or execute arbitrary Sonic Pi code through a simple interface.
Before using the MCP server, add this code to your Sonic Pi buffer to handle OSC messages:
live_loop :code_runner do
use_real_time
code = sync "/osc*/run-code"
# Since we receive the code as a string, we can use eval to execute it
# The code comes as the first element of the message
begin
eval(code[0].to_s)
rescue Exception => e
puts "Error executing code: #{e.message}"
end
end
Make sure this code is running in Sonic Pi before using the MCP server.
Add to ~/.cursor/mcpServers.json
:
{
"mcpServers": {
"sonic_pi_mcp": {
"name": "Sonic Pi MCP",
"command": "bunx",
"args": ["sonic-pi-mcp"],
"transport": {
"type": "stdio"
}
}
}
}
Add to ~/Library/Application Support/Claude/claude_desktop_config.json
:
{
"mcpServers": {
"sonic_pi_mcp": {
"command": "bunx",
"args": ["sonic-pi-mcp"],
}
}
}
Plays a single note with customizable parameters.
Parameters:
note
(required): MIDI note number (0-127)synth
(optional): Synth to use (e.g., ":saw", ":beep", ":prophet")sustain
(optional): Note duration in seconds (default: 1)cutoff
(optional): Filter cutoff frequency (default: 100)Example:
// Play middle C with saw wave synth
{
"name": "play_note",
"parameters": {
"note": 60,
"synth": ":saw",
"sustain": 0.5,
"cutoff": 80
}
}
Executes arbitrary Sonic Pi code.
Parameters:
code
(required): Sonic Pi code to executeExample:
{
"name": "run_code",
"parameters": {
"code": "use_synth :prophet\nplay_pattern_timed [60, 64, 67], [0.5]"
}
}
Here are some example interactions using the MCP tools:
// Play a C major arpeggio
{
"code": `
use_synth :piano
play_pattern_timed [60, 64, 67, 72], [0.25], release: 0.1
`
}
// Create a rhythmic pattern
{
"code": `
live_loop :rhythm do
use_synth :tb303
play choose(chord(:C3, :minor)), release: 0.2, cutoff: rrand(60, 120)
sleep 0.25
end
`
}
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "sonic_pi_mcp" '{"name":"Sonic Pi MCP","command":"bunx","args":["sonic-pi-mcp"],"transport":{"type":"stdio"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"sonic_pi_mcp": {
"name": "Sonic Pi MCP",
"command": "bunx",
"args": [
"sonic-pi-mcp"
],
"transport": {
"type": "stdio"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"sonic_pi_mcp": {
"name": "Sonic Pi MCP",
"command": "bunx",
"args": [
"sonic-pi-mcp"
],
"transport": {
"type": "stdio"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect