MCP-AppleMusic
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| itunes_playB | Start playback in Music (iTunes). |
| itunes_pauseB | Pause playback in Music (iTunes). |
| itunes_nextA | Skip to the next track. |
| itunes_previousB | Return to the previous track. |
| itunes_searchB | Search the Music library for tracks whose names contain the given query. Returns a list of tracks formatted as "Track Name - Artist". |
| itunes_play_songA | Play the first track whose name exactly matches the given song name. Returns a confirmation message. |
| itunes_create_playlistA | Create a new playlist with the given name and add tracks to it. 'songs' should be a comma-separated list of exact track names. Returns a confirmation message including the number of tracks added. |
| itunes_libraryB | Return a summary of the Music library, including total tracks and user playlists. |
| itunes_current_songB | Get information about the currently playing track. Returns the track name, artist, and album. |
| itunes_all_songsB | Get a list of all songs in the Music library. Returns a formatted list of all tracks with their names and artists. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have distinct purposes, but there is some overlap between itunes_play and itunes_play_song, as both involve starting playback. However, itunes_play is a general playback start, while itunes_play_song targets a specific song, which helps differentiate them. All other tools are clearly distinct in function.
All tool names follow a consistent snake_case pattern with the prefix 'itunes_' and a descriptive verb or noun phrase. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming style.
With 10 tools, the server is well-scoped for managing an Apple Music library, covering essential operations like playback control, library queries, playlist creation, and song search. Each tool serves a clear purpose without redundancy, making the count appropriate for the domain.
The tool set provides good coverage for core music library management, including playback, search, and playlist creation. However, there are minor gaps, such as the inability to delete or modify existing playlists, which could limit some agent workflows. Overall, it supports most common tasks effectively.