music-assistant/server

Music Assistant is a free, opensource Media library manager that connects to your streaming services and a wide range of connected speakers. The server is...

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on May 9th, 2019
Open Issues & Pull Requests: 81 (+0)
GitHub issues: Enabled
Number of forks: 620
Total Stargazers: 3,108 (+0)
Total Subscribers: 23 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.2 hours
Mean response time: 221.7 days
90th percentile: 1550.6 days
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 2
Closed in 7 days: 2
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 2
Closed in 7 days: 2
Comments in 7 days: 1
Events in 7 days: 2

Top labels

  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Music Assistant Server is a media library manager that aggregates streaming services and connected speakers into a unified interface.

The tool solves the problem of managing music across multiple streaming sources and speaker systems by centralizing them through a single server application. It connects to various streaming services and speaker devices, allowing unified control and library management. The server runs as a persistent background process on always-on hardware such as Raspberry Pi, NAS devices, or Intel NUC machines, making it suitable for home environments where continuous availability is expected.

Music Assistant is designed primarily for users who want to integrate music management with home automation, particularly those already using Home Assistant. The recommended installation method is as a Home Assistant add-on, though Docker containers are also officially supported. The tool is not distributed through PyPI because it depends on external system components including ffmpeg with specific codec support, native libraries like jemalloc, and bundled binaries that a standard Python package installation cannot provide. For development work, users can run from source by providing their own Python and ffmpeg installations.

The project maintains active issue tracking and feature request channels through separate repositories. Development occurs in Python with a focus on system integration, requiring management of multiple external dependencies and OS-level components. The codebase includes automated testing via pytest and enforces code quality through pre-commit hooks integrated into the development workflow.