Spotify MCP Server

Instructions

Implementation Reference

• src/spotify.ts:512-524 (handler)

  Core handler implementation in SpotifyService that fetches playlist tracks from the Spotify API using the /playlists/{playlistId}/tracks endpoint.
  async getPlaylistTracks( token: string, playlistId: string, limit: number = 50 ): Promise<PagingObject<PlaylistTrack>> { const id = this.extractId(playlistId); const params = { limit: Math.min(limit, 50) }; return await this.makeRequest<PagingObject<PlaylistTrack>>( `playlists/${id}/tracks`, token, params ); }
• src/mcp/tools/playlists.ts:99-149 (registration)

  MCP tool registration including title, description, input schema using Zod, and thin handler that delegates to SpotifyService.getPlaylistTracks.
  get_playlist_tracks: { title: "Get Playlist Tracks", description: `Get the complete track listing from any playlist with detailed song information and metadata. 🎯 USE CASES: • Extract songs from playlists for custom music apps • Analyze musical patterns and genre distributions • Create backup copies or derivative playlists • Study playlist curation and track progression • Build recommendation systems based on playlist contents 📝 WHAT IT RETURNS: • Complete ordered track listing from the playlist • Song titles, artists, albums, and release dates • Track durations, popularity scores, and preview URLs • Added date and user who added each track • Explicit content flags and market availability 🔍 EXAMPLES: • "Get all tracks from my 'Road Trip' playlist" • "Show me songs in playlist ID: 1BxfuPKGuaTgP6aM0NMpti" • "List tracks from Spotify's RapCaviar playlist" • "Extract songs from this collaborative party playlist" 🎵 TRACK DETAILS: • Maintains original playlist order and context • Shows track addition history and contributors • Includes full metadata for each song • Perfect for playlist analysis and music research • Great for creating similar or inspired playlists 💡 ANALYSIS OPPORTUNITIES: • Genre distribution and musical diversity • Track popularity trends within playlists • Artist frequency and collaboration patterns • Temporal patterns in track additions ⚠️ REQUIREMENTS: • Valid Spotify access token • Playlist must be accessible to the user • Respect rate limits for large playlists`, schema: createSchema({ token: commonSchemas.token(), playlistId: commonSchemas.spotifyId("playlist"), limit: commonSchemas.limit(1, 50, 50), }), handler: async (args: any, spotifyService: SpotifyService) => { const { token, playlistId, limit = 50 } = args; return await spotifyService.getPlaylistTracks(token, playlistId, limit); }, },
• src/mcp/tools/playlists.ts:140-144 (schema)

  Input schema definition for the get_playlist_tracks tool using createSchema with token, playlistId, and optional limit parameters.
  schema: createSchema({ token: commonSchemas.token(), playlistId: commonSchemas.spotifyId("playlist"), limit: commonSchemas.limit(1, 50, 50), }),
• src/mcp/tools/index.ts:22-36 (registration)

  Central registry where playlistTools (containing get_playlist_tracks) is spread into the allTools object used by the MCP server.
  export const allTools: ToolsRegistry = { ...albumTools, ...artistTools, ...trackTools, ...playlistTools, ...playbackTools, ...userTools, ...searchTools, };