Make music from inside an assistant on the person's own account
One company's docs show a full fit.
What counts as done
The assistant reads the remaining credits, confirms the spend before more than one generation, makes the track and returns a playable file or link in the same session, without the person leaving the chat.
How agents ask for it: make me a song with Suno
, use my Suno credits for this
, generate the music in Claude
, make the track and save it to my library
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Mubert API F Mubert Inc. | The Mubert MCP server connects by browser credential paste or by header for headless clients, get_capabilities and mubert://usage report quota left before spending, mutating tools are separated, and get_track returns the download URL and expiry in the session. source |
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| ElevenLabs Music API BB Eleven Labs Inc. | The hosted MCP server now generates music through Flow nodes on the person's workspace credits over OAuth, but returns a Flow link, documents no credit read or spend confirmation, warns each retry charges again, and the Claude directory connector can't make music. source |
| Soundverse API E Soundverse Inc. | The Soundverse MCP server signs in with OAuth and spends the person's plan tokens, with per-tool approval in Claude. The finished track stays in the Soundverse Library and doesn't play in the chat, and no credit read is documented. source |
| Suno MCP F Suno, Inc. (United States, terms governed by Massachusetts law) | Built for this: OAuth from Claude, ChatGPT, Gemini, Cursor or Claude Code, all plans, a credits check, and credits:spend and download scopes. No spend cap or confirmation is documented, the page still has early access, and acc-22 found it unusable headless. source |
Doesn't do this job 8
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Beatoven.ai API F Beatoven Private Limited (with subsidiary Beatoven Inc.) | A bearer-token API; no MCP server or assistant connection is documented. source |
| fal music models BB Features & Labels, Inc. | fal bills its own prepaid key; it doesn't connect an assistant to the person's Suno or ElevenLabs account. source |
| Google Lyria D Google LLC | A key-billed Gemini API model; no MCP server or consumer-account route for music is documented. source |
| Loudly Music API F Loudly GmbH | A single-key B2B API; no MCP server or assistant connection is documented. source |
| MusicGPT API D MusicGPT Ltd | A key-billed API with an npm SDK; no MCP server or account connection for assistants in the docs index. source |
| MusicGen on Replicate B Replicate, LLC | A token-billed model API; no connection to a person's music account. source |
| SOUNDRAW API F SOUNDRAW Inc. | A contract-and-token B2B API; no MCP server or assistant connection. source |
| Stable Audio API F Stability AI Ltd (UK, EU, Switzerland) and Stability AI US Services Corporation (elsewhere) | A key-billed REST API; no MCP server or account connection for assistants is documented. source |
What stops agents finishing
- OAuth-only MCP server can't be used by a headless worker (acc-22)
- tools return library ids rather than files, so the take can't be handed on (acc-23)
- no documented cap or confirmation on spending credits
- plugin config placeholder never substituted, every tool fails (acc-17)
- early-access form before the server works
Around it
Before: personal-assistants.chat-request. After: file-storage.upload-file, music-distribution.release.
Where this comes from
Weight 12 of 100 in Music generation: 5 of 43 links: GitHub issues wiring Suno MCP and the ElevenLabs MCP server into agent tools, and two HN posts
The same as data: /api/v1/use-cases/music-generation.assistant-account.json, or the MCP tool get_use_case with id music-generation.assistant-account. Other jobs in this category: /api/v1/niches?category=music-generation.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.