mcp-sonic-pi: MCP server for Sonic Pi
LocalAbout mcp-sonic-pi: MCP server for Sonic Pi
mcp-sonic-pi connects MCP clients to a running Sonic Pi instance, enabling music creation through English-language requests. It is for Sonic Pi users who want to control music creation through an MCP client.
Key features
- 01Connects MCP clients to Sonic Pi
- 02Creates music from English requests
- 03Runs through uvx
- 04Requires Sonic Pi to be running
Use cases
- 01Create music with natural-language requests
- 02Use Sonic Pi through an MCP client
MCP support
The MCP server connects clients to Sonic Pi so they can create music using English-language requests.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEmcp-sonic-pi: MCP server for Sonic Pi
mcp-sonic-pi connects any MCP client with Sonic Pi enabling you to create music with English.
Requirements
- Python 3.10+
- Sonic Pi installed and running
Quickstart
Start using mcp-sonic-pi with an MCP client by running:
uvx mcp-sonic-pi
To start using this MCP server with Claude, add the following entry to your claude_desktop_config.json:
{
"mcpServers": {
"sonic-pi": {
"args": [
"mcp-sonic-pi"
],
"command": "/path/to/uvx"
}
}
}
Note: Ensure Sonic Pi is running before starting the MCP server.
Contributing
Contributions are welcome! Please feel free to submit a pull request.
License
This project is licensed under the Apache 2.0 License - see the LICENSE file for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.