Mopidy-MPD is an extension that provides a full MPD server implementation to make Mopidy available to MPD clients. It is bundled with Mopidy and enabled by default.
As a simple security measure, the MPD server is by default only available
from localhost. To make it available from other computers, change the
mpd/hostname config value. Before you do so, note that the MPD
server does not support any form of encryption and only a single clear
text password (see
mpd/password) for weak authentication. Anyone
able to access the MPD server can control music playback on your computer.
Thus, you probably only want to make the MPD server available from your
local network. You have been warned.
MPD stands for Music Player Daemon, which is also the name of the original MPD server project. Mopidy does not depend on the original MPD server, but implements the MPD protocol itself, and is thus compatible with clients for the original MPD server.
For more details on our MPD server implementation, see
This is a non exhaustive list of MPD features that Mopidy doesn’t support. Items on this list will probably not be supported in the near future.
- Only a single password is supported. It gives all-or-nothing access.
- Toggling of audio outputs is not supported
- Channels for client-to-client communication are not supported
- Stickers are not supported
- Crossfade is not supported
- Replay gain is not supported
statsdoes not provide any statistics
decodersdoes not provide information about available decoders
The following items are currently not supported, but should be added in the near future:
- Modifying stored playlists is not supported
tagtypesis not supported
- Live update of the music database is not supported
See Configuration for general help on configuring Mopidy.
[mpd] enabled = true hostname = 127.0.0.1 port = 6600 password = max_connections = 20 connection_timeout = 60 zeroconf = Mopidy MPD server on $hostname command_blacklist = listall,listallinfo
If the MPD extension should be enabled or not.
Which address the MPD server should bind to.
- Listens only on the IPv4 loopback interface
- Listens only on the IPv6 loopback interface
- Listens on all IPv4 interfaces
- Listens on all interfaces, both IPv4 and IPv6
Which TCP port the MPD server should listen to.
The password required for connecting to the MPD server. If blank, no password is required.
The maximum number of concurrent connections the MPD server will accept.
Number of seconds an MPD client can stay inactive before the connection is closed by the server.
Name of the MPD service when published through Zeroconf. The variables
$portcan be used in the name.
Set to an empty string to disable Zeroconf for MPD.
List of MPD commands which are disabled by the server. By default this setting blacklists
listallinfo. These commands don’t fit well with many of Mopidy’s backends and are better left disabled unless you know what you are doing.