supercollider-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| synth-executeC | SynthDefのコードを生成し、そのコードを実行して音を出します。 コードは{}でくくるようにしてください。 |
| multi-synth-executeC | 複数のSynthDefを同時に実行します。 |
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 2 tools
The two tools have clearly distinct purposes: multi-synth-execute runs multiple SynthDefs simultaneously, while synth-execute generates and executes code for a single SynthDef to produce sound. There is no overlap or ambiguity between these functions.
Both tools follow a consistent verb_noun pattern with hyphen separation (multi-synth-execute and synth-execute), using the same root terms and structure. The naming is predictable and coherent throughout the set.
With only 2 tools, the server feels thin for a domain like SuperCollider audio synthesis, which typically involves more operations such as defining, modifying, stopping, or querying synths. The count is too low for comprehensive coverage of the apparent scope.
The tool set is severely incomplete for audio synthesis workflows; it lacks essential operations like creating or loading SynthDefs, stopping or freeing synths, controlling parameters, or managing audio server state. This will likely cause agent failures in typical use cases.