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 :ref:`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 :ref:`ext-http` to control Mopidy.
Mopidy extensions can make additional web APIs available through Mopidy's builtin web server by implementing the :ref:`http-server-api`. Web clients can use the :ref:`http-api` to control Mopidy from JavaScript.
See the Mopidy extension registry to find a number of web clients can be easily installed as Mopidy extensions.
There are a few Mopidy web clients that are not installable as Mopidy extensions:
Lastly, there are several web based MPD clients, which doesn't use the :ref:`ext-http` frontend at all, but connect to Mopidy through the Mopidy-MPD frontend. For a list of those, see the "Web clients" section of the MPD wiki's clients list.
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.
MPRIS is a specification that describes a standard D-Bus interface for making media players available to other applications on the same system.
See the Mopidy-MPRIS documentation for a survey of some MPRIS clients.