MiniMax-Music3-Jam

Describe any song in plain English. An LLM writes the title, the tagged lyrics and the three-part structured caption (Global Metadata / Vocal Details / Arrangement) from the official prompting guide, then MiniMax Music 3 generates the full song with vocals. Songs can be shared to a community feed (stored in the victor/minimax-music3-community bucket, each with its creation date).

How it works

• Compose (CPU): composer.py calls an LLM on the HF Inference Router and returns {title, tags, lyrics, global_metadata, vocal_details, arrangement}.
• Sing (ZeroGPU): engine.py is the diffusers ModularPipeline port of MiniMax Music 3 with the AoTI kernels from diffusers-internal-dev/MiniMax-Music3-aoti (same path as the official Space). Cover art comes from Z-Image-Turbo in the same GPU allocation.
• Share: WAV + cover + meta.json are written to the bucket mounted at /data; the feed is served from memory.

API

• POST /create(description, audio_duration, seed, community, instrumental) streams status JSON then the final result {audio, title, tags, lyrics, caption, seed, duration, created_at, thumbnail?, community_url?}.
• POST /generate(caption, lyrics, audio_duration, seed, title, tags, community) for explicit inputs.
• POST /community() returns the newest shared songs.

The same three endpoints are also exposed as MCP tools (create, generate, community) via Gradio's built-in mcp_server=True — schema and description come straight from each function's type hints and docstring, no extra code. MCP endpoint (streamable HTTP): https://victor-minimax-music3-jam.hf.space/gradio_api/mcp (legacy SSE transport at /gradio_api/mcp/sse; add ?tools=create,community to either to expose only a subset).

Requires the HF_TOKEN secret (composer LLM) and the bucket volume hf://buckets/victor/minimax-music3-community:/data.