supercollider-mcp
# SuperCollider MCP Server
The SuperCollider MCP Server is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server for the SuperCollider programming language that allows to execute synth using supercolliderjs.
## Prerequisites
1. Install [SuperCollider](https://supercollider.github.io/downloads) on your machine.
2. Node.js and npm should be installed on your machine. You can download it from [Node.js official website](https://nodejs.org/).
## Compatibility
This project has been tested and confirmed to work only on macOS with Apple Silicon (M1) processors. Compatibility with other operating systems or processor architectures has not been verified.
## Installation
### Usage with Claude Desktop
Add this to your `claude_desktop_config.json`:
```json
{
"mcpServers": {
"mcp-supercollider": {
"command": [
"npx",
"-y",
"@makotyo/mcp-supercollider"]
}
}
}
```
### Usage with VS Code
Add the following JSON block to your User Settings (JSON) file in VS Code. You can do this by pressing Ctrl + Shift + P and typing Preferences: Open User Settings (JSON).
Optionally, you can add it to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.
> Note that the mcp key is not needed in the .vscode/mcp.json file.
```json
{
"mcp": {
"servers": {
"mcp-supercollider": {
"command": "npx",
"args": [
"-y",
"@makotyo/mcp-supercollider"
]
}
}
}
}
```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.