mcp-applemusic
Related Servers
Alternatives to mcp-applemusic
No user-submitted related servers found.
Related Servers
- 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.4 npm1MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for controlling Apple Music on macOS using JXA (JavaScript for Automation). Manage playback, search tracks, create playlists, and more without API keys.17 npmMIT
- AlicenseAqualityCmaintenanceA safe, structured Model Context Protocol server for the local Apple Music app on macOS. It lets an MCP client inspect a library, analyze and manage playlists, control playback, edit supported metadata, and keep a local audit trail.18MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Apple Music that lets AI assistants manage playlists, control playback, and browse the music library.108MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for controlling Apple Music on macOS via AppleScript, enabling playlist management, playback control, and library search through natural language.17 npm1MIT
- AlicenseNot gradedqualityAmaintenanceCreate custom playlists, control apple music locally, search apple music catalog, use ai to generate play lists, and more all without needing an apple developer account or giving the MCP server special privileges.MIT
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.