Announcing toolforest.io a personal project that links your chatbot to ListenBrainz (and more)

Today I’m releasing toolforest.io, a personal project that links ListenBrainz to AI assistants such as Claude and ChatGPT. It works with their free tiers and allows you to do things such as create a wrapped-style summary of your listening history or search for artists you like who may be performing in your area soon. You can learn about the project and try it out here: About - toolforest.io .
I hope you find toolforest.io both useful and enjoyable and welcome your suggestions and comments (positive or negative).

Cheers,
Gerrit

1 Like

Cool to see more tools using ListenBrainz data!

Toolforest maintains a replicated MusicBrainz and ListenBrainz database

Our servers appreciate the consideration!
Generally, the more you can do without using the API, the better for us.

I do see that some features use the API such as fuzzy matching or metadata lookups.
For your information, those have been put behind key, so the LB user token is required to use them: Making sure you're not a bot!

1 Like

Thanks for taking a look. I can assure you that I am neither a bot nor a meat-puppet controlled by one :slight_smile: I am using the public API for playlist management, recommendations, and also fetching recent (< 24h) listens since they are replicated on a daily cadence. Older listens are fetched from my replica.

I’m using a local Typesense DB + Postgres replica for metadata and fuzzy track lookup so this should eliminate the need to hit the public APIs for many operations.

1 Like

That’s because of the “Making sure you’re not a bot!” above? :smiley: That’s unfortunately triggered by the anti bot measures on the blog, and it is directed towards the forum, not you. I think it is supposed to allow the MB forum, but that doesn’t seem to work. If all would work as it should show the blog post title.

3 Likes

Hello @gbw614 !

We’ve added API endpoints that will be very useful for your MCP, and will save a lot of resources for us.
You can now programmatically request a user history export zip to get the whole history in one go, instead of hitting the /listens endpoint page by page: User history exports — ListenBrainz 0.1.0 documentation

I even implemented time ranges thinking of your tool, which I had tested by asking it to generate a playlist of artists I used to listen to years ago but don’t listen to anymore.
With that in mind the export endpoints allow you to define a time range for the export, specifically for this sort of use cases.

Thanks in advance for helping us reduce our API traffic :slight_smile:

3 Likes

Hi @gbw614,

Great work on this! I’ve been looking into toolforest.io and find the approach to linking ListenBrainz to AI assistants really compelling.

I’m currently in the progress of implementing it into “Sorana”, a personal desktop AI knowledge workspace and agent harness I’m building (forum thread here). Before I go too far down the rabbit hole, I wanted to check if the project is still in active development?

If so, are there any recommended patterns or best practices for integrating it into a custom, local-first agent harness? I’d be happy to share feedback or suggestions as I test it out.

Cheers!