This is a list of MPD clients we either know works well with Mopidy, or that we know won’t work well. For a more exhaustive list of MPD clients, see http://mpd.wikia.com/wiki/Clients.
A console client that works well with Mopidy, and is regularly used by Mopidy developers.
Search does not work in the “Match if tag contains search phrase (regexes supported)” mode because the client tries to fetch all known metadata and do the search on the client side. The two other search modes works nicely, so this is not a problem.
With ncmpcpp <= 0.5, the library view is very slow when used together with
Mopidy-Spotify. A workaround is to edit the ncmpcpp configuration file
~/.ncmpcpp/config) and set:
media_library_display_date = "no"
With this change ncmpcpp’s library view will still be a bit slow, but usable.
Note that this option was removed in ncmpcpp 0.6, but with this version, the library view works well without it.
A console client. Works with Mopidy 0.6 and upwards. Uses the
command, but in a resource inefficient way.
GMPC is a graphical MPD client (GTK+) which works well with Mopidy.
GMPC may sometimes requests a lot of meta data of related albums, artists, etc. This takes more time with Mopidy, which needs to query Spotify for the data, than with a normal MPD server, which has a local cache of meta data. Thus, GMPC may sometimes feel frozen, but usually you just need to give it a bit of slack before it will catch up.
Sonata is a graphical MPD client (GTK+). It generally works well with Mopidy, except for search.
When you search in Sonata, it only sends the first to letters of the search query to Mopidy, and then does the rest of the filtering itself on the client side. Since Spotify has a collection of millions of tracks and they only return the first 100 hits for any search query, searching for two-letter combinations seldom returns any useful results. See #1 for details.
The following web clients use the MPD protocol to communicate with Mopidy. For other web clients, see HTTP clients.