- Home
- MCP servers
- SuperCollider
SuperCollider
- typescript
2
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"brada1878-mcp-wave": {
"command": "node",
"args": [
"/absolute/path/to/supercollider-mcp/dist/index.js"
],
"env": {
"SCLANG_PATH": "/Applications/SuperCollider.app/Contents/MacOS/sclang"
}
}
}
}You can control SuperCollider audio synthesis in real time using a dedicated MCP server. It translates natural language descriptions into sound, manages the SuperCollider lifecycle, sequences patterns, records audio, and even executes raw SuperCollider code, all through a typed, safe interface.
How to use
You interact with the server through an MCP client to boot the SuperCollider engine, play sounds from natural language prompts, run sequences, and record outputs. Start by booting the server, then issue synthesis requests using the high-level tooling provided. You can stop all sounds at any time or inspect the current server state to monitor CPU usage and running synths. For advanced control, you can run raw SuperCollider code and start/stop recordings as needed.
How to install
Prerequisites you need before installing: Node.js 18 or later and a local installation of SuperCollider.
# Install dependencies
npm install
# Build the MCP server
npm run build
Additional setup and configuration
If you installed SuperCollider in a non-standard location, set the environment variable SCLANG_PATH to the path of sclang. You can optionally set SCSYNTH_PATH if you have a custom synths location.
export SCLANG_PATH="/path/to/sclang"
# Optional: export SCSYNTH_PATH="/path/to/scsynth"
Client configuration example (MCP integration)
When configuring an MCP client to connect to this server, you typically point to a local stdio-based runner that executes the MCP entry point. The following example shows the command and argument structure you would use from a client configuration.
{
"mcpServers": {
"supercollider": {
"command": "node",
"args": ["/absolute/path/to/supercollider-mcp/dist/index.js"]
}
}
}
Available tools
sc_health_check
Validate that SuperCollider is installed correctly and the path is configured.
sc_boot
Boot the SuperCollider audio server to start synthesis.
sc_quit
Quit the SuperCollider server and release resources.
sc_status
Query current server status, including CPU usage and active synths.
sc_play_synth
Play a synthesized sound described in natural language or presets without manual parameter tuning.
sc_play_synth_advanced
Play a specific synth with explicit numeric parameters for exact control.
sc_play_pattern
Play a rhythmic pattern or melodic sequence over time.
sc_stop_all
Immediately stop all currently playing synths.
sc_execute
Execute raw SuperCollider code for advanced control.
sc_record_start
Begin recording the audio output to a file.
sc_record_stop
Stop the current recording session.