I really love this app but there is no api.
I could not use my codex to process my playlist.
I really need a api or mcp.

Where is your playlist coming from, eg what format is it?

What sort of API would you want/need?

Don't know why i can't add long content here,so i organize them to the txt file.

And them i found that i can't add txt file here,Can i reply you at the mail?
: )

You can upload your file here:
https://www.mixo.dj/uploads

Failed to upload one or more files.
There have some bugs.

Hi Remko,
Thanks for getting back to me.
I’m a DJ, and most of my playlists come from Rekordbox. The interchange format I care about most is Rekordbox XML, with M3U8 or JSON as useful fallbacks.
I’ve also been vibe-coding my own macOS DJ library and player because I couldn’t find a tool that quite matched my workflow. It works, but it’s still a rough prototype. I only recently discovered MIXO, and after trying it, I realized it already covers roughly 70% of what I need.
The remaining 30% is less about supporting another file format and more about making the library programmable.
MCP itself isn’t the core requirement. A documented local API would already be very useful, with MCP acting as an adapter for Codex or other AI tools. I’d mainly want read and write access to:

• Tracks and metadata, including BPM, key, rating, comments, and tags
• Playlists and smart playlists, including track membership and order
• Tags, search, and filters
• Cue points, if possible
Some concrete use cases would be:
• Find tracks in a playlist that are missing energy or mood tags
• Group tracks by mood, energy, genre, or venue
• Suggest tags and place them in a review queue
• Build or reorder a set playlist and write it back to MIXO
I also have two product suggestions.
I saw that MIXO already supports custom tags and filtering. What I’d love is a stronger tag aggregation layer: grouping tags into facets such as mood, energy, or venue, showing track counts, combining multiple tags, and saving the result as a smart playlist.
The second is optional AI-assisted semantic analysis. In my own prototype, I connect to the Gemini API. In MIXO, I could imagine analyzing selected tracks or playlists, suggesting mood, energy, genre, or set fit, and letting the DJ review every suggestion before anything is written back.
Would a local API—or even a read-only API as a first step—fit how MIXO is built? I’d be happy to share a small list of endpoints and use cases, or test an early version.