We still have a few blockers for proper streaming support. But we are slowly but surely getting closer to have something like that working.

https://github.com/mopidy/mopidy/issues?labels=EOS&state=ope...

The use case that I'd be really excited about -- and something that I have been strongly considering hacking MPD to do -- would not be an icecast stream to my phone, but for my phone to have its own Mopidy or MPD instance.

Right now, at work, I simply NFS mount my home music library, and then sync my mpd tag cache over periodically. This works while I'm in one location, at work, but would not work on my cell phone; I don't have a network protocol that would survive it, and MPD has no real support for high-latency filesystems (it doesn't know to go fetching the next file in advance, nor does it know to go cache a few megabytes -- or the next few songs -- in case the data link goes away).

Mopidy's extension support is pretty exciting, then! It seems like it should be relatively possible to concoct a 'mopidy.remote' extension that knows how to do these things, and the corresponding server-side for a Mopidy instance running at home.

Have you folks thought of this sort of use case? Am I about to reinvent the wheel?

yes, you can access it remotely. mopidy is an MPD server, so any platform that has a compatible MPD client should be able to access it. The docs list a lot of the available clients and their compatibility with mopidy:

http://docs.mopidy.com/en/latest/#clients

You can control mopidy remotely, but not yet stream to remote clients.

Mopidy is lacking some important features of mpd itself