SuperCollider MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCLANG_PATH | No | Custom path to the sclang executable if SuperCollider is installed in a non-standard location | |
| SCSYNTH_PATH | No | Optional custom path to the scsynth executable |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sc_health_checkA | Check if SuperCollider is installed and configured correctly. Run this first if you have issues. |
| sc_bootA | Boot the SuperCollider audio server. Must be called before any sound synthesis. |
| sc_quitA | Quit the SuperCollider audio server and clean up resources. |
| sc_statusA | Get the current status of the SuperCollider server (running, CPU usage, etc.) |
| sc_executeB | Execute raw SuperCollider code. Use this for advanced synthesis control or custom SynthDefs. |
| sc_play_synthA | Play a synthesized sound based on a natural language description. This is the primary tool for sound synthesis. Examples: "play a bell sound at C4", "play a low bass tone for 2 seconds", "play a plucked string sound" |
| sc_play_synth_advancedB | Play a specific synth with explicit parameters. Available synths: sine, pluck, bell, bass, pad, kick, snare, hihat, atmosphere, sweep |
| sc_play_patternB | Play a rhythmic pattern or sequence of notes. Useful for creating melodies, beats, or musical phrases. |
| sc_record_startB | Start recording audio output to a file |
| sc_record_stopB | Stop recording audio |
| sc_stop_allA | Stop all currently playing synths immediately |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools have distinct purposes, but sc_play_synth and sc_play_synth_advanced could cause confusion as both handle sound synthesis with overlapping functionality. The descriptions help differentiate them, with sc_play_synth using natural language and sc_play_synth_advanced offering explicit synth selection, but an agent might misselect between them for certain tasks.
All tool names follow a consistent sc_verb_noun pattern with snake_case throughout, such as sc_boot, sc_execute, and sc_play_pattern. This predictability makes it easy for agents to understand and navigate the toolset without naming confusion.
With 11 tools, the count is well-scoped for an audio synthesis server, covering essential operations like booting, playing sounds, recording, and cleanup. Each tool earns its place by addressing a specific aspect of the SuperCollider workflow without being excessive or insufficient.
The toolset provides comprehensive coverage for core audio synthesis tasks, including server management, sound playback, recording, and monitoring. Minor gaps exist, such as the lack of tools for modifying or deleting recorded files or adjusting synth parameters mid-playback, but agents can work around these with existing tools like sc_execute for advanced control.