Skip to main content
Glama

Related Servers

Alternatives to mcp-applemusic

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      High-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 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A 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.
      18
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Create 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

    B3.4/5.0

    Scored across 66 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues