Apple Music MCP Server

What is Apple Music MCP Server?

Apple Music MCP Server is an MCP (Model Context Protocol) server for interacting with the Apple Music API. It provides tools for searching songs and generating playback links, enabling AI assistants to access Apple Music content through a standardized interface.

How to use Apple Music MCP Server?

Build and run the server using cargo install --path . and cargo run -- --team-id TEAM_ID --key-id KEY_ID --private-key-path /path/to/key.p8. Authentication credentials (Apple Developer Team ID, Key ID, and private key file) are provided via command-line arguments; an optional --storefront flag (default: jp) sets the Apple Music storefront.

Key features of Apple Music MCP Server

• Search for songs by title, artist, or album
• Generate deep links for songs and playlists
• Command-line interface with configurable storefront
• Uses the Model Context Protocol (MCP)

Use cases of Apple Music MCP Server

• Search Apple Music catalog from AI assistants
• Generate playback links for songs or playlists
• Integrate Apple Music access into MCP-compatible tools

FAQ from Apple Music MCP Server

What does the server do?

It provides MCP tools (searchSongs and generatePlaybackLink) that allow clients to query the Apple Music catalog and produce playback deep links.

What are the runtime requirements?

Rust (nightly) and an Apple Developer account with Apple Music API access are required. The server expects a valid Apple Music API Key (.p8 file).

How do I authenticate?

Pass your Apple Developer Team ID, Key ID, and the path to your private key (.p8 file) as command-line arguments: --team-id, --key-id, and --private-key-path.

What is the default storefront and can I change it?

The default storefront is jp (Japan). You can change it with the --storefront flag (e.g., --storefront us).

What tools does the server expose?

Two tools: searchSongs (accepts a query string, returns song details) and generatePlaybackLink (accepts song_id or playlist_id, returns a playback URL).