One approach to follow when organizing your server actions is for example the CRUD naming that follows your database tables.
So you will have folders same as database tables names and below then actions like get, list, insert, update and delete.
This way at least you can find the right database actions pretty quickly.
The rest of the general actions or combined actions you should group by major functionally part so they all make sense when searching.
I think this falls in the “ best practices” and maybe other people working with larger project can share their logical organization