sonic-pi-mcp

# sonic-pi-mcp `sonic-pi-mcp` is a Python MCP server that lets an MCP client control a local Sonic Pi runtime over the standard `stdio` transport. It starts Sonic Pi's Ruby daemon, sends OSC messages to the Spider runtime, runs Sonic Pi code, stops jobs, reads runtime events/logs, and searches the local Sonic Pi docs/samples/synthdefs. ## Requirements - Python 3.11+ - A local Sonic Pi installation or checkout. - The Sonic Pi root directory must contain: - `app/server/ruby/bin/daemon.rb` - `app/server/ruby/bin/spider-server.rb` - usually `etc/doc`, `etc/samples`, and `etc/synthdefs` No machine-specific path is baked into this package. Set `SONIC_PI_ROOT` in the MCP client environment unless you pass `root_path` to `sonic_start`. ## Install From PyPI: ```bash pip install sonic-pi-mcp ``` From a local checkout: ```bash pip install . ``` Build a wheel/sdist: ```bash python -m build ``` Then install the wheel on another machine: ```bash pip install dist/sonic_pi_mcp-*.whl ``` The wheel only contains the Python package under `src/sonic_pi_mcp`. Generated runtime files, exported audio, examples, tests, and local scripts are excluded from distribution. ## Configuration Required in most deployments: ```text SONIC_PI_ROOT=<path to the Sonic Pi root directory> ``` Useful optional variables: ```text SONIC_PI_MCP_RUNTIME_DIR=<writable directory for temporary run_file buffers> SONIC_PI_MCP_STARTUP_TIMEOUT=60 SONIC_PI_MCP_KEEPALIVE_INTERVAL=4 SONIC_PI_MCP_EVENT_BUFFER_SIZE=5000 SONIC_PI_MCP_DEFAULT_COLLECT_MS=1500 SONIC_PI_HOME=<custom Sonic Pi user-home root for logs, if needed> ``` `SONIC_PI_MCP_RUNTIME_DIR` is used when code is too large for Sonic Pi's OSC packet size and must be submitted with `run_file`. If it is not set, the server uses a per-user cache directory such as `%LOCALAPPDATA%\sonic-pi-mcp` on Windows, `~/Library/Caches/sonic-pi-mcp` on macOS, or `${XDG_CACHE_HOME:-~/.cache}/sonic-pi-mcp` on Linux. PowerShell example without hard-coding…