Mopidy-MPD

This extension implements an MPD server to make Mopidy available to MPD clients.

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 mopidy.frontends.mpd.

Limitations

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.

  • 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
  • stats does not provide any statistics
  • decoders does 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
  • tagtypes is not supported
  • Browsing the file system is not supported
  • Live update of the music database is not supported

Dependencies

None. The extension just needs Mopidy.

Default configuration

[mpd]
enabled = true
hostname = 127.0.0.1
port = 6600
password =
max_connections = 20
connection_timeout = 60
zeroconf = Mopidy MPD server on $hostname

Configuration values

mpd/enabled

If the MPD extension should be enabled or not.

mpd/hostname

Which address the MPD server should bind to.

127.0.0.1
Listens only on the IPv4 loopback interface
::1
Listens only on the IPv6 loopback interface
0.0.0.0
Listens on all IPv4 interfaces
::
Listens on all interfaces, both IPv4 and IPv6
mpd/port

Which TCP port the MPD server should listen to.

mpd/password

The password required for connecting to the MPD server. If blank, no password is required.

mpd/max_connections

The maximum number of concurrent connections the MPD server will accept.

mpd/connection_timeout

Number of seconds an MPD client can stay inactive before the connection is closed by the server.

mpd/zeroconf

Name of the MPD service when published through Zeroconf. The variables $hostname and $port can be used in the name.

Set to an empty string to disable Zeroconf for MPD.

Usage

The extension is enabled by default. To connect to the server, use an MPD client.

Connecting from other machines on the network

As a secure default, Mopidy only accepts connections from localhost. If you want to open it for connections from other machines on your network, see the documentation for the mpd/hostname config value.

If you open up Mopidy for your local network, you should consider turning on MPD password authentication by setting the mpd/password config value to the password you want to use. If the password is set, Mopidy will require MPD clients to provide the password before they can do anything else. Mopidy only supports a single password, and do not support different permission schemes like the original MPD server.

Table Of Contents

Previous topic

Mopidy-Local

Next topic

Mopidy-Stream

This Page