Mopidy is a music server written in Python: it owns the music library, the queue and the playback, and whatever you actually touch – a browser tab, a phone, a terminal, a desktop client – connects to it as a separate program. Stein Magnus Jodal started it in 2009 and it is now developed by the Mopidy organisation on GitHub; the current release is 4.0.5, published on 16 October 2026, under the Apache License 2.0.
Mopidy is deliberately just a server. Out of the box it plays music from the local disk and Internet radio, and it runs its own web server on port 6680; install the Mopidy-MPD extension and it also speaks the Music Player Daemon protocol on port 6600, so the population of existing MPD clients works against it. Everything else is an extension: music sources (Spotify, SoundCloud, TIDAL, YouTube, Bandcamp, the Internet Archive, Jellyfin, Subsonic-compatible servers, podcasts, radio directories) and front ends (Iris, the MusicBox web client, a mobile remote, an API explorer) are separately installed packages.
That split is the point. The server sits next to the speakers – a small home server, a NAS, a Raspberry Pi wired to a DAC – and several people can search, queue and skip at the same time from their own devices, because the state lives in the server rather than in one app. The project’s own summary is blunt about it: Mopidy is an extensible music server written in Python, and the extension index is the real product surface.
mopidy.conf holds the core settings plus a section per installed extension, so a headless server is configured as text that can be versioned and copied to a new machine.Mopidy 4 needs Python 3 and GStreamer 1.x with decoders for the formats you play; on Debian 12 that means python3-gi, gir1.2-gstreamer-1.0, gir1.2-gst-plugins-base-1.0 and the gstreamer1.0-plugins-* packages. Linux and macOS are the documented targets – the download page lists PyPI, the project’s own Debian/Ubuntu and Raspberry Pi apt repositories, and Homebrew – and there is no official Windows build.
There is no GUI to install: the server reads ~/.config/mopidy/mopidy.conf, starts with the mopidy command and is normally run as a systemd service. A minimal setup is the core package plus Mopidy-Local for a searchable library, Mopidy-MPD and/or Mopidy-Iris for control, and an audio output on the host; mopidy local scan builds the library index. Because it is a server, it is happiest on a machine that stays on and stays connected to the speakers.