
SoundBerry
ai.soundberryPublished by soundberry.aiOfficial publisherv1.0.0Updated Oct 24, 2026
AI music tools for producers: generate tracks and stems, split stems, detect tempo and key.
Overview
SoundBerry gives an assistant AI music production tools: generating tracks and stems, splitting stems, and detecting tempo and key.
- What you can do
- Generate music tracks and individual stems from a prompt or request through SoundBerry's AI music tools. Split an existing track into its separate stems. Detect the tempo and musical key of audio.
- When to use it
- Useful for music producers and audio creators who want an assistant to draft tracks, isolate stems for remixing or editing, or quickly find the tempo and key of a piece of audio without leaving the chat. It is not a general-purpose audio editor. It is aimed at music production tasks. It is not aimed at general audio editing. It is not aimed at general audio editing. It is not aimed at general audio editing. It is not aimed at general audio editing. It is not aimed at general audio editing. It is
- Requirements
- A remote endpoint at soundberry.ai over streamable HTTP. A SoundBerry API key is required, passed as a Bearer token in the Authorization header. The key is created in the SoundBerry dashboard. Network access is needed.
Installation
In SourceWeft
- Open SoundBerry in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.soundberry%2Fsoundberry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"soundberry": {
"type": "http",
"url": "https://soundberry.ai/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestOct 24, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.