Creative · Community report
Build a playlist generator app
A creator reports building a playlist generator app inside Muse with a Spotify connector and a custom data source. This page covers how to ask for it and what to check.
What you can get
- Prepare
A Spotify account authorised through Muse's Spotify connector
- Ask and review
Authorise the Spotify connector and decide what it may do: read your library, create playlists, or both.
- Check the result
A working playlist-building app plus a record of what the connector and routine did; not a hosted product or a licence to republish music data.
The source case
@vibecodeguild reports using Muse's built-in Spotify connector plus a custom connector they made for a second music service to build an app that generates playlists. They say it cost nothing to build and ran entirely inside Muse, so there was no hosting or security setup, and that Spotify does not expose its recommendation engine through its API, which is why the second source was needed. The author says it needed some correction to get a routine that crawls songs for related tracks, and they finished with a 70s funk disco look. The post is a video description; the playlists, code and connector details are not in the text.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
It was all free to build, and it's all inside Meta Muse so I don't have to waste time with hosting or security settings.
Source excerpt
Spotify doesn't actually expose their music recommendation engine via their API
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring A Spotify account authorised through Muse's Spotify connector, A second music-data source with an API you may use (the post names one by a shortened link only), Seed songs or artists and a target playlist length, A visual style, if you want one. Source community report, checked 2026-10-16.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
What you need
You supply
- A Spotify account authorised through Muse's Spotify connector
- A second music-data source with an API you may use (the post names one by a shortened link only)
- Seed songs or artists and a target playlist length
- A visual style, if you want one
How to try it
Editorial, not from the source
- Authorise the Spotify connector and decide what it may do: read your library, create playlists, or both.
- Pick the second data source for related tracks and check its terms and API access before pointing Muse at it.
- Ask Muse to build the routine starting from a few seed songs, with a cap on how many tracks it will crawl.
- Review the first playlist before it is saved; expect to correct the routine, as the author reports having to.
- Ask for the look and layout last, once the playlists are right.
- Ask Muse to list the connectors and permissions the finished app holds, and remove any you no longer need.
What @vibecodeguild built
The author starts from a limitation: Spotify's API, they say, does not expose the recommendation engine that powers its own suggestions. Their workaround was to bring in a second music-data service through a custom connector they made, then have their Muse agent (they call it Gus) write a routine that crawls songs using that data to find related tracks and assemble playlists.
They also say it needed correction along the way and that they gave the finished app a 70s funk disco look. They describe the whole thing as a video demonstration for people learning to get started; the text of the post gives no output.
Choices the post leaves to you
A crawl-based routine can make a lot of requests. Cap the number of tracks and set a stop rule so one playlist does not turn into hundreds of calls to a service with its own rate limits; the post does not say how the author handled this.
Check the second service's terms before you build on it. Whether you may store or display its data, and whether a free tier covers a routine that crawls, is general due diligence rather than something the post addresses. Also decide whether the app may write to your Spotify account or only read from it.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- The post gives no code, playlist output or connector configuration; only the author's description is available.
- The second music service appears only as a shortened link, so its name, terms and limits are not confirmed here.
- "Free to build" is the author's statement; the post does not cover usage limits or whether the app keeps running.
- The "correction" the author mentions is not detailed, so the effort required is unknown.
- This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.
If it goes wrong
Editorial, not from the source
- The playlist is full of obvious or repeated tracks
- Change the seed songs, ask Muse to exclude artists already in the list, and limit how many tracks come from one artist.
- The related-track source stops answering
- It may be rate limiting. Lower the crawl size and check the service's limits; the post does not say what limits applied.
Common questions
Can Muse build a Spotify playlist app?
One creator reports it did, using the built-in Spotify connector and a custom connector for a second data source. The post does not show the code or output, and this guide has not reproduced it.
Why did the author need a second data source?
By their account, Spotify does not expose its recommendation engine through its API, so related-track data came from the other service.
Did it work first time?
The author says they had to do some correction to build the crawling routine. What was corrected is not described.
Next
Related to this task
More in Creative
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.