SuperCollider MCP Server
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
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 handles multiple SynthDefs simultaneously, while synth-execute focuses on generating and executing code for a single SynthDef. There is no overlap or ambiguity between their 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. This makes them predictable and easy to understand.
With only two tools, the server feels under-scoped for a domain like SuperCollider, which typically involves complex audio synthesis and manipulation. This limited set may not cover essential operations like parameter adjustment, effect chaining, or file management.
The tool surface is severely incomplete for audio synthesis workflows. It lacks basic operations such as stopping synths, modifying parameters, loading/saving definitions, or managing audio output, which are critical for practical use in this domain.