SoundGen (soundgen.ai)

ai.soundgenPublished by soundgen.aiOfficial publisherv1.0.0Updated Nov 4, 2026

Browser DAW for AI assistants: build multitrack songs with MIDI, effects, stems and generation.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server that lets an assistant build multitrack songs in a browser DAW, working with MIDI, effects, stems and generation.

What you can do
  • Build and arrange multitrack songs in a browser-based DAW.
  • Work with MIDI parts, effects and stems inside a project.
  • Generate audio material as part of a song.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to help compose, arrange or generate music in a DAW-style project rather than just describe it, for example sketching a multitrack idea or producing stems.
Requirements
A remote endpoint at soundgen.ai over streamable HTTP. Authentication is required: an Authorization header carrying a bearer token, which is a SoundGen API key starting with sgk_, created on the provider's site under Settings > Integrations.
Before you install
The server requires a SoundGen API key sent in the Authorization header; treat it as a secret and check what the provider does with project and audio data. Generation may consume paid quota or credits, and edits to songs or projects change stored data.

Installation

In SourceWeft

  1. Open SoundGen (soundgen.ai) in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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.soundgen%2Fsoundgen/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "soundgen-soundgen-ai": {
      "type": "http",
      "url": "https://soundgen.ai/api/mcp-server",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 4, 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.