Apple Music MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| music_healthA | Check platform, Music availability, JXA connectivity, and writable object kinds. |
| music_get_player_stateA | Return playback state, current track, position, volume, shuffle, repeat, and EQ. |
| music_get_library_summaryA | Return track and playlist counts without returning the full library. |
| music_list_playlistsC | List playlists with stable IDs, kinds, parents, counts, and mutation capabilities. |
| music_get_playlistA | Get one playlist by persistent ID. |
| music_list_playlist_tracksA | List a playlist's tracks in current order with opaque pagination. |
| music_search_tracksC | Search or browse local library tracks with metadata filters and stable IDs. |
| music_get_tracksA | Resolve up to 500 persistent track IDs while preserving request order. |
| music_analyze_libraryA | Run deterministic library or playlist analysis without sending every track to the AI. |
| music_list_playback_targetsA | List AirPlay outputs and EQ presets, including active selections. |
| music_control_playbackC | Control playback or play a local track/playlist by persistent ID. |
| music_set_playback_optionsB | Set volume, mute, shuffle, repeat, EQ, and AirPlay output selection. |
| music_plan_changesB | Validate library mutations and return a 10-minute, single-use approval token. |
| music_get_change_planA | Read a pending or completed plan without exposing approval token hashes. |
| music_cancel_change_planB | Cancel a pending plan without changing Music. |
| music_apply_changesA | Apply an approved plan after token, expiry, and optimistic concurrency checks. |
| music_list_changesA | List persistent audit history without exposing stored before/after metadata. |
| music_plan_undoA | Create a normal preview-and-approval plan for the reversible part of a prior change. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| organize_library | Analyze a local library and propose safe playlist changes. |
| clean_playlist | Find duplicates and stale entries in one playlist and propose cleanup. |
| build_playlist | Select local tracks from criteria and create a new ordered playlist. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| apple_music_capabilities | Machine-readable supported and intentionally excluded capabilities. |
| apple_music_safety | Rules clients must follow before mutating Music. |
TDQS
Scored across 18 tools
Each tool has a clearly distinct purpose: plan lifecycle, library browsing, playback control, and health checks. The plan-related tools are differentiated by their role (create, read, cancel, apply, list, undo), and there is no ambiguity between similar names.
All tools follow a consistent snake_case verb_noun pattern prefixed with music_ (e.g., get_playlist, list_playlists, control_playback). The only slight deviation is music_health, but it's a conventional health-check noun and does not disrupt the overall pattern.
18 tools is slightly above the typical 3–15 range, but the count is justified by the domain's breadth (library, playback, change planning, and system health). Each tool serves a distinct function, and there is no redundancy or bloat.
The tool set covers the full lifecycle: library retrieval and search, playlist management, playback control and options, change planning with approval and undo, and audit history. No critical operations are missing for a comprehensive Apple Music server.