urmusic-mcp
Related Servers
Alternatives to urmusic-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables ChatGPT to control Spotify playlists, playback (including exact-cue seek), and perform offline metadata export to ZIP.-
- FlicenseAqualityDmaintenanceA lightweight MCP server that enables AI assistants like Cursor and Claude to control Spotify playback, playlists, and manage tokens via OAuth.152-
- FlicenseNot gradedqualityCmaintenanceA lightweight MCP server that enables AI assistants to control Spotify playback and manage playlists.-
- FlicenseBqualityBmaintenanceA local music retrieval MCP server that lets users search, download, and organize songs via natural language, with lyrics matching from NetEase Cloud Music and LRCLIB, plus local library indexing through SQLite.5-
- AlicenseAqualityBmaintenanceMCP server for querying your local Google Takeout activity (Search/YouTube history) via SQLite/FTS5. Provides tools for keyword search, activity stats, and database info, enabling AI assistants to cite your personal history.3MIT
- AlicenseNot gradedqualityAmaintenanceA local MCP server for managing and organizing a personal QQ Music library, enabling playlist operations, music analysis, and intelligent classification workflows with safe write-back and rollback.4MIT
TDQS
Scored across 7 tools
Each tool targets a clearly distinct purpose: raw SQL querying, dormant artist discovery, artist expansion via MusicBrainz, artist profile, yearly review, top albums, and schema introspection. Even listening_year_in_review vs listening_top_albums are explicitly disambiguated in their descriptions (grouping by artist vs album).
All tools follow a consistent listening_verb_noun pattern (query, find_dormant, expand_artist, artist_profile, year_in_review, top_albums, schema). The verb_noun structure is uniform and predictable throughout.
Seven tools is a well-scoped set for a listening-history MCP server. Each tool earns its place: data access, schema introspection, and several distinct analytical/exploratory queries.
The surface covers the main listening-history use cases well: raw querying, artist profiles, top albums, yearly review, dormant-artist leads, and artist expansion. A minor gap is the lack of a broader 'top artists all-time' tool independent of a specific year, though listening_query could cover it.