Find a file
2025-11-05 11:48:00 -05:00
.devcontainer refactor(frontend): Migrate tailwind config to v4 2025-11-04 14:17:51 +00:00
.github try with double quotes 2025-11-05 11:48:00 -05:00
.vscode refactor(frontend): Migrate tailwind config to v4 2025-11-04 14:17:51 +00:00
assets docs: Update screenshot 2024-07-09 09:51:33 -04:00
config docs: Update listenbrainz json example to include url 2025-10-29 14:50:21 +00:00
docker/root/etc/s6-overlay/s6-rc.d refactor(mpris): Remove socat service in favor of simplified dbus connection 2025-07-08 19:53:55 +00:00
docsite docs: Improve sources documentation 2025-11-04 19:18:46 +00:00
flatpak chore: Update flatpak description 2025-03-31 12:12:28 -04:00
patches feat(icecast): Switch to metadata-only parsing 2025-03-19 16:34:19 +00:00
public Update index.html 2024-01-19 11:05:34 -05:00
src chore(frontend): Update sass package and vite config to remove deprecation warnings 2025-11-04 14:36:22 +00:00
.dockerignore chore: Add docker-compose dev file and vscode task 2024-12-05 09:37:58 -05:00
.gitignore refactor(cache): Update file cache name and gitignore 2025-09-11 19:14:01 +00:00
.lnav.config.json docs: Add lnav config 2024-12-27 18:49:29 +00:00
.mocharc.json test: Setup transient di cache 2025-09-11 19:14:01 +00:00
.nvmrc chore(!): Upgrade Node to LTS for --import support 2024-02-15 12:40:02 -05:00
.nycrc.json refactor: Restructure server directory 2023-08-24 11:12:27 -04:00
alpine.Dockerfile docs(fix): Add missing docsite build steps to alpine docker variant 2024-07-15 13:50:37 -04:00
cliff.toml chore: Add git-cliff template 2023-06-07 10:01:30 -04:00
CONTRIBUTING.md chore: Refactor git/dev workflow to use master as unstable branch 2024-08-30 09:53:52 -04:00
docker-compose.dev.yml chore: Add docker-compose dev file and vscode task 2024-12-05 09:37:58 -05:00
docker-compose.yml docs: Update Spotify docs and usage due to Redirect URI changes 2025-08-01 17:28:16 +00:00
Dockerfile feat(docker): Paralellize npm install and build processes 2025-01-16 20:48:05 +00:00
eslint.config.js Improve testing, linting, and node usage in devcontainer 2024-10-08 19:33:47 +00:00
index.html Update index.html 2024-01-19 11:05:34 -05:00
LICENSE Create LICENSE 2020-12-06 21:51:20 -05:00
package-lock.json chore(frontend): Update sass package and vite config to remove deprecation warnings 2025-11-04 14:36:22 +00:00
package.json chore(frontend): Update sass package and vite config to remove deprecation warnings 2025-11-04 14:36:22 +00:00
README.md docs: Improved linking on config/landing and configuration type refinement 2025-11-04 18:49:16 +00:00
tsconfig.json feat: Improve client/source schema validation generation and error handling 2024-10-09 12:18:23 -04:00
vite.config.ts chore(frontend): Update sass package and vite config to remove deprecation warnings 2025-11-04 14:36:22 +00:00

multi-scrobbler

Latest Release License: MIT Docker Pulls Docs

multi-scrobbler logo

A javascript app to scrobble music you listen to, to Maloja, Last.fm, ListenBrainz, and other services.

Quick Start Guide

Why should I use this over a browser extension and/or mobile app scrobbler?

  • Platform independent -- Because multi-scrobbler communicates directly with service APIs it will scrobble everything you play regardless of where you play it. No more need for apps on every platform you use!
  • Open-source -- Get peace of mind knowing exactly how your personal data is being handled.
  • Track your activity regardless of where you listen -- Scrobble from many Sources to one Client with ease and without duplicating tracks.
  • Manage scrobbling for others -- Scrobble for your friends and family without any setup on their part. Easily silo sources to specific clients to keep plays separate.

But I already scrobble my music to Last.fm/ListenBrainz, is multi-scrobbler for me?

Yes! You can use Last.fm as a Source or Listenbrainz as a Source to forward scrobbles from your profile to any other Client! That way you can keep your current scrobble setup as-is but still get the benefit of capturing your data to a self-hosted location.

How Does multi-scrobbler (MS) Work?

You set up configurations for one or more Sources and one or more Clients. MS monitors all of your configured Sources. When new tracks are played by a Source MS grabs that information and then sends it (scrobbles it) to all Clients that Source is configured to forward to.

Source

A Source is a data source that contains information about music you are playing or have listened to, like a desktop player, web music player, or cloud music service. Examples are Spotify, Jellyfin, Plex, Youtube Music, Navidrome, etc...

Source configurations consist of:

  • A friendly name.
  • Any data needed to communicate or authenticate with the Source.
  • An optional list of Client names that the Source should scrobble to. If omitted the Source also scrobbles to all configured Clients.

Client

A Client is an application that stores the historical information about what music you have played (scrobbles). Examples are Maloja, Last.fm, Listenbrainz...

Client configurations consist of:

  • A friendly name.
  • Any data needed to communicate or authenticate with the Client.

Quick Start

See the Quick Start Guide

Installation

See the Installation documentation

Configuration

See the Configuration documentation

Usage

A status page with statistics, recent logs, and some runtime configuration options can be found at

http://localhost:9078

Output is also provided to stdout/stderr as well as file if specified in configuration.

On first startup you may need to authorize Spotify and/or Last.fm by visiting the callback URL (which can also be accessed from the status page). Visit the status page above to find the applicable link to trigger this.

Help/FAQ

Having issues with connections or configuration? Check the FAQ before creating an issue!

Development

Detailed architecture and development guides for Sources/Clients

License

MIT