Once Mopidy is up and running, you need a client to control it.
Note that clients only control Mopidy. The audio itself is not streamed to the clients, but it is played on the computer running Mopidy. This is by design, as Mopidy was originally modelled after MPD. If you want to stream audio from Mopidy to another device, the primary options are Icecast and Snapcast.
The most popular ways to control Mopidy are with web clients and with MPD clients.
In addition, alternative frontends like Mopidy-MPRIS and Mopidy-Raspberry-GPIO provides additional ways to control Mopidy. Alternative frontends that use a server-client architecture usually list relevant clients in the extension’s documentation.
There are many clients available that use Mopidy-HTTP to control Mopidy.
See the Mopidy extension registry to find a number of web clients can be easily installed as Mopidy extensions.
Non-extension web clients¶
There are a few Mopidy web clients that are not installable as Mopidy extensions:
MPD is the protocol used by the original MPD server project since 2003. The Mopidy-MPD extension provides a server that implements the same protocol, and is compatible with most MPD clients.
There are dozens of MPD clients available. Please refer to the Mopidy-MPD extension’s documentation for an overview.