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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/BradA1878/mcp-wave'
If you have feedback or need assistance with the MCP directory API, please join our Discord server