Mopidy

An extensible music server in Python that plays local files, internet radio and streaming services, controlled from MPD or web clients.

8.6k stars, 728 forks Python On GitHub since December 2009

Visit website View on GitHub How to run it

Mopidy at a glance

Open sourceYes, Apache-2.0No paid parts in the repository
Health67 of 100Actively developed
Self-hostingFrom sourceSteps in the README
InterfaceEnglish onlyNo translation files found
Release rhythmEvery ~22 daysLatest: v4.0.5, 16 October 2026

What is Mopidy?

Mopidy runs on a computer or Raspberry Pi connected to speakers and plays music from local disk, SoundCloud, internet radio and other sources through extensions, including a Spotify backend. You control it from any MPD client or web interface on a phone, tablet or computer, so the whole household can queue songs on one player. Packages exist for Debian, Ubuntu, Raspberry Pi OS, Arch Linux and macOS.

Good fit if

  • You want a networked jukebox for a living room or hi-fi setup without a commercial streaming box.
  • You already use MPD clients and want more music sources.

Look elsewhere if

  • You want to stream your library to many devices and listeners: Navidrome.
  • You need synchronized playback in several rooms: Snapcast.

Before you adopt it

Mopidy is Apache-2.0 and has no paid parts. Nearly every recent commit comes from one developer, even though the project dates back to 2009. Most features live in separate extensions, so check that the ones you need are maintained.

Drafted with AI from the project's README and repository data, then checked against that data on 31 October 2026. Report a correction

How to run Mopidy yourself

Docker
No Docker files in the repository
Compose file
None in the repository
Setup effort
Not rated: no compose file to judge from
Kubernetes
No Helm chart in the repository
Desktop and mobile
No app builds in GitHub releases
Interface languages
English only

Install instructions: mopidy.com or the README on GitHub.

Mopidy health: is it still maintained?

67 of 100, actively developed

Release rhythmEvery ~22 daysLatest: v4.0.5, 16 October 2026
Issue repliesNot measuredToo few recent issues from outside the team
Bus factorHigh riskThe most active of 3 authors wrote 97% of recent commits
  • Activity
    261 commits in the last 90 days, the latest on 2 November 2026.
    29 / 30
  • Contributors
    3 people wrote the latest 100 commits; the most active wrote 97% of them.
    5 / 20
  • Releases
    6+ releases in the last 12 months; the latest, v4.0.5, on 16 October 2026.
    17 / 20
  • Replies to issues
    Too few recent issues from outside the team to measure, so this part gets a neutral score.
    10 / 20
  • Security practices
    OpenSSF Scorecard 6.2 of 10.
    6 / 10

Read from GitHub on 5 November 2026. How the score works

Mopidy security practices

OpenSSF Scorecard checks how a project is developed and released: reviews, protected branches, pinned dependencies, signed releases. It does not audit the code itself.

OpenSSF Scorecard6.2 of 10How the project is built and released
Security policyNoNo SECURITY.md or similar

What each check found

  • Binary files10 / 10No compiled binaries checked into the repository
  • Dangerous workflows10 / 10No risky patterns in GitHub Actions
  • License file10 / 10A license file is present
  • Maintained10 / 10Steady commits and issue activity in the last 90 days
  • Packaging10 / 10Releases are published as packages from CI
  • Pinned dependencies10 / 10Dependencies and build tools use fixed versions
  • Token permissions10 / 10CI tokens have only the rights they need
  • Branch protection4 / 10Rules on the main branch are partly enforced
  • Best-practices badge0 / 10No OpenSSF Best Practices badge
  • Code review0 / 10Changes are merged without review
  • Fuzzing0 / 10No fuzz testing found
  • Security policy0 / 10No security policy
  • Static analysis0 / 10No static analysis found

From the OpenSSF Scorecard of 2 November 2026. Checks that do not apply to Mopidy are left out.

Mopidy license: is it open source?

Mopidy uses Apache-2.0, an open-source license approved by the OSI.

  1. December 2009First published on GitHub.
  2. TodayApache-2.0.

Mopidy for developers

Written in

  • Python 100%
  • HTML <1%
  • CSS <1%
  • Roff <1%
  • Shell <1%

Getting involved

Contributing guideNot foundNo CONTRIBUTING file in the repository
Open issues152On GitHub
Authors, 90 days3Of the latest 100 commits

Language shares are GitHub’s count of the code in the repository.

Alternatives to Mopidy

  • Beetsmusic library manager and MusicBrainz tagger 82 health · MIT · 15.9k stars
  • koelMusic streaming solution that works. 74 health · MIT · 17.3k stars
  • KodiKodi is an award-winning free and open source home theater/media center software and entertainment hub for… 71 health · GPL-2.0 · 21.4k stars
  • JellyfinThe Free Software Media System - Server Backend & API 94 health · GPL-2.0 · 59k stars
  • AudiobookshelfSelf-hosted audiobook and podcast server 83 health · GPL-3.0 · 14.9k stars

All 18 projects in Media servers & streaming

Questions about Mopidy

Is Mopidy open source?

Yes. Mopidy is published under Apache-2.0, an OSI-approved open-source license.

Is Mopidy still maintained?

Its health score is 67 of 100 (actively developed). It had 261 commits in the last 90 days, the latest on 2 November 2026, and its latest release came out on 16 October 2026.

How do I run Mopidy?

The repository has no Docker files or app builds, so you build it from source. The README on GitHub has the steps.

What is Mopidy written in?

Mopidy is written mainly in Python (100% of the code), by GitHub’s count of the repository.

What are the alternatives to Mopidy?

Close alternatives in the Media servers & streaming category include Beets, koel, Kodi.