music-warehouse-mcp
Related Servers
Alternatives to music-warehouse-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes a self-hosted SQLite master of a user's complete Last.fm listening history over Streamable HTTP with OAuth 2.1, so ChatGPT or Claude can answer questions about any date range without hitting the Last.fm API. Provides 32 tools covering recent plays, period rankings, range comparisons, artist listening intensity, session segmentation, and shifts in taste over time.14 npmMIT
- FlicenseNot gradedqualityAmaintenanceConnects 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.-
- AlicenseBqualityDmaintenanceEnables AI agents to access public Spotify data (tracks, albums, artists, playlists, podcasts) without an API key, including lyrics and podcast transcripts with optional login.281,423 PyPI316MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to a self-hosted Your Spotify instance and Spotify's Web API for deep listening analytics and playback control. It enables users to query unlimited listening history, generate custom Wrapped summaries, and manage playlists through natural language.18Apache 2.0
- AlicenseAqualityBmaintenanceLets AI assistants answer questions about your Spotify listening history, including taste evolution, top artists, recently played, and playlist analysis.872 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely connect to a user's personal Discogs music collection for mood-aware searching, analytics, and context-aware recommendations via Cloudflare Workers.MIT
TDQS
Scored across 14 tools
Most tools target clearly distinct query types: name search, raw plays, top lists, daily counts, entity histories, Wrapped summaries, precomputed aggregates, and live Spotify state. Some overlap remains between top_artists/top_tracks, get_stat aggregates, get_wrapped, and stored vs live recent plays, but descriptions provide explicit guidance on when to use which.
All names use readable snake_case with no camelCase or chaotic variation. The set is not a strict verb_noun pattern throughout, since many tools are noun phrases like artist_history, now_playing, and spotify_top, but the convention is still predictable and consistent.
Fourteen tools fits comfortably within the ideal 3-15 range for an analytics-style server. Each tool covers a distinct listening-history or Spotify-live query, and there is no excessive filler or fragmentation.
The surface strongly covers read-only listening analytics: search, raw plays, top artists/tracks, daily counts, artist/track histories, on-this-day, Wrapped, precomputed stats, and live Spotify tools. Minor gaps remain, such as no direct per-artist or per-track query over an arbitrary date range beyond top lists, and no metadata/import management, but core workflows are covered.