applemusic

The Apple Music MCP Server exposes a set of tools that let clients search the Apple Music catalog and generate playback links using the Model Context Protocol (MCP). Once the server is running, you can connect with an MCP client to invoke the available tools. The primary capabilities are: 1) searchSongs - query Apple Music by song title, artist, or album to retrieve a list of matching tracks with metadata such as title, artist, album, duration, and URLs; 2) generatePlaybackLink - create a deep link for playback of a specific song or playlist using its identifier. These tools enable rich discovery and seamless playback experiences within MCP-enabled clients. You interact with the server via its command-line options to provide Apple Music API credentials, after which the server handles authentication and API requests on your behalf.

To use the server, start it with your Apple Music credentials and storefront. The CLI-based tooling exposed by the server then accepts requests for searching and link generation. When invoking searchSongs, provide a query string to receive structured results. When invoking generatePlaybackLink, provide either a song_id or a playlist_id to receive a Apple Music URL suitable for playback in supported clients.

Prerequisites:

• Rust nightly toolchain installed (recommended by the project requirements)
• Access to the Apple Music API with a private key (.p8) and associated team and key IDs

Installation steps:

1. Ensure Rust nightly is installed and in use. You can install via rustup and set the toolchain to nightly: rustup install nightly rustup default nightly

2. Build and install the MCP server from source: cargo install --path .

3. Run the server (examples assume you have your Apple Music credentials ready): cargo run -- --team-id YOUR_TEAM_ID --key-id YOUR_KEY_ID --private-key-path /path/to/AuthKey.p8

4. Verify the server starts and note any required configuration (such as storefront defaults, which can be overridden with --storefront): --storefront <STOREFRONT> (e.g., us, jp)

Notes and tips:

• The server requires an Apple Music API private key (.p8) and associated credentials (team-id and key-id). Ensure the private key path is correct and accessible by the running process.
• The default storefront is set to jp if not provided; use --storefront to switch to the desired region (e.g., us, jp).
• If you encounter authentication errors, double-check that the Apple Developer account has Apple Music API access and that the key is valid.
• The server exposes a CLI interface for searching songs and generating playback links; ensure your MCP client can format requests according to the MCP specification used by the server.
• Since this is a Rust-based server, you will typically deploy in environments where Rust toolchain is available, or you can build a release binary and run it standalone.