navidrome-mcp
Related Servers
Alternatives to navidrome-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceConnects AI assistants to a local music library for full-text search and filtering of tracks, albums, artists, genres, composers, and lyrics, plus listening analytics and metadata hygiene audits. Also lets users generate and populate playlists and control playback (play, pause, seek, volume) in a running player instance.-
- AlicenseNot gradedqualityBmaintenanceProvides Last.fm listening analytics and recommendations by combining Last.fm and MusicBrainz metadata, maintaining a local listening index, and recording explicit preferences. Enables queries for listening summaries, taste profiles, artist context, and evidence-backed recommendations via MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceGenerates .m3u playlists on the user's PC based on their current mood or theme, using metadata from local music files.5GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables an agent to pull a public or unlisted YouTube playlist with no credentials, infer language, genre and mood tags per track, slice the results into mood-based playlists using declarative YAML rules, and export them as spreadsheets, M3U files or an HTML build console. It also covers publishing, either through quota-aware resumable API jobs or free browser import links, with write operations requiring explicit confirmation and defaulting to dry runs.MIT
- FlicenseNot gradedqualityCmaintenanceEnables music search, metadata retrieval, local audio analysis (tempo, key, energy), recommendations, song recognition, and classical work resolution via Spotify, Last.fm, AudD, MusicBrainz, and Songkick APIs.-
- AlicenseCqualityCmaintenanceSyncs YouTube Music liked songs, analyzes them for DJ metadata like BPM and key, and enables creating playlists from previews.10MIT
TDQS
Scored across 15 tools
Most tools have distinct purposes, but create_playlist vs create_smart_playlist and update_playlist vs commit_daylist could cause confusion. Descriptions help clarify boundaries, though an agent might occasionally select the wrong one.
The majority follow a verb_noun pattern (list_, delete_, create_, update_), but a few depart with noun phrases like similar_tracks, listening_history, and daylist_context. The names are still readable and predictable, with no chaotic mixes.
15 tools is at the upper edge of the ideal range, but each tool addresses a distinct facet of the library/playlist domain. The count feels justified and not bloated.
Playlist CRUD is well covered, including smart playlists. Minor gaps exist: no direct way to edit smart playlist rules, and no standalone track detail tool. However, search_tracks and update_playlist cover most needs.