mcp-applemusic
Related Servers
Alternatives to mcp-applemusic
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceGives MCP clients control of Apple Music playlists, library, catalog, discovery, playback, and the Up Next queue. Runs on macOS, Windows, and Linux using Music.app, Safari, the Apple Music API, or Chrome, requiring only a Mac or an Apple Music subscription.-
- FlicenseNot gradedqualityAmaintenanceGives MCP clients control of Apple Music playlists, library, catalog, discovery, playback, and the Up Next queue, using four interchangeable engines that run on macOS, Windows, and Linux. Requires only a Mac or an Apple Music subscription, with the API engine needing no browser or Music app at all.-
- AlicenseNot gradedqualityBmaintenanceHigh-efficiency Apple Music MCP Server featuring a dual-engine architecture (macOS Native JXA + Cloud REST API), cross-platform chart discovery (Shazam,Spotify, YouTube), async parallel batch additions, pure-audio enforcement, and zero-timeout execution.6 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables any MCP client to search the catalog, manage playlists, library and folders, control playback and the Up Next queue, and read ratings, recommendations and charts. Runs on macOS, Windows and Linux using local Music.app, Safari or Chrome sessions, or Apple's web API, requiring only a Mac or an Apple Music subscription.-
- FlicenseNot gradedqualityAmaintenanceEnables controlling Apple Music playlists, library, catalog discovery, playback, and the Up Next queue from any MCP client, using Music.app, Safari, Chrome, or the Apple Music API. Runs on macOS, Windows, and Linux, with a mode preference that picks the best available engine per call.-
- FlicenseNot gradedqualityAmaintenanceGives any MCP client control of Apple Music playlists, library, catalog search and discovery, playback, and the Up Next queue, driving Music.app, Safari, Chrome, or the web API across macOS, Windows, and Linux. A Mac or a signed-in subscription is enough, and the local library plus playback work with no account at all on macOS.-
TDQS
Scored across 66 tools
Mostly distinct resources with clear descriptions, but several overlapping pairs exist: favorite_song (by title) vs favorite_track (currently playing) is a genuinely confusing split, and search vs search_catalog vs play_song have overlapping discoverability concerns. DJ auto-transition also overlaps conceptually with set_track_start_finish for trimming purposes.
Very consistent itunes_verb_noun snake_case convention throughout, making the suite predictable. Deductions for mixing 'song' and 'track' terminology arbitrarily (favorite_song vs favorite_track vs rate_track), using bare verbs in itunes_play/pause/next, and the odd itunes_import_from_spotify which breaks the pattern.
66 tools is excessive for coherence; this is well into the bloat category. While the domain is broad, many tools could be consolidated (e.g., favorite and rate variants by scope, or the multiple set_device functions). Even a complete music player control surface struggles to justify this many distinct entry points.
The surface is remarkably complete: full playlist CRUD, playback control, metadata editing, stats/reporting, AirPlay device management, folder organization, search, lyrics, even Spotify import and share-link generation. If anything, it over-covers the domain, providing far more than a typical agent would ever need.