SpotifyScraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_SP_DC | No | Spotify sp_dc cookie value to enable authenticated tools such as lyrics and podcast transcripts. Optional. |
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 |
|---|---|
| get_trackA | Fetch a track by URL, URI, or 22-character ID. |
| get_albumC | Fetch an album (with its tracks) by URL, URI, or ID. |
| get_artistB | Fetch an artist by URL, URI, or ID. |
| get_playlistB | Fetch a playlist by URL, URI, or ID (up to |
| get_episodeB | Fetch a podcast episode by URL, URI, or ID. |
| get_showB | Fetch a podcast show (with episodes) by URL, URI, or ID. |
| searchC | Search across tracks, albums, artists, playlists, shows, and episodes. |
| list_chartsA | List the built-in editorial charts (key, name, backing playlist id). |
| get_chartB | Fetch an editorial chart (e.g. 'top-50-global') as a playlist. |
| get_related_artistsC | Fetch artists related to an artist ('fans also like'). |
| get_discographyB | Fetch an artist's full discography (albums, singles, compilations). |
| get_similar_albumsC | Recommend albums similar to a track. |
| get_colorsA | Extract a cover image's theming colors (image URL/uri, or any entity URL/URI/ID). |
| get_artist_eventsC | Fetch an artist's upcoming concerts/events. |
| get_tracksB | Fetch many tracks at once; one ordered result per input, failures captured per item. |
| get_albumsA | Fetch many albums at once; one ordered result per input, failures captured per item. |
| get_artistsA | Fetch many artists at once; one ordered result per input, failures captured per item. |
| get_episodesB | Fetch many episodes at once; one ordered result per input, failures captured per item. |
| get_playlistsA | Fetch many playlists at once (up to |
| get_showsB | Fetch many shows at once (up to |
| get_canvasC | Fetch a track's Canvas looping video (needs SPOTIFY_SP_DC). |
| get_creditsA | Fetch a track's credits — performers, writers, producers (needs SPOTIFY_SP_DC). |
| get_userC | Fetch a public user profile (needs SPOTIFY_SP_DC). |
| get_lyricsB | Fetch a track's lyrics (needs SPOTIFY_SP_DC). |
| get_transcriptB | Fetch a podcast episode's transcript (needs SPOTIFY_SP_DC). |
| get_accountA | Fetch the logged-in account's product state (needs SPOTIFY_SP_DC). |
| get_cover_imageC | Return an entity's cover art as an inline image.
|
| get_track_visualsA | Fetch a track plus its cover
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| describe_album | Prompt: describe an album's vibe. |
| playlist_blurb | Prompt: write a short blurb for a playlist. |
| summarize_episode | Prompt: summarize a podcast episode from its transcript. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Each tool has a clearly distinct purpose: single-entity fetchers, batch fetchers, search, charts, related data, visuals, lyrics, etc. No two tools overlap in functionality; even the composite get_track_visuals is unique.
The predominant pattern is 'get_<entity>' (singular or plural), with a few exceptions like 'list_charts' and 'search'. This is mostly consistent, but the mix of 'get_' and 'list_' and the absence of a prefix for 'search' are minor deviations.
28 tools is on the high side, but each tool serves a specific data retrieval need for Spotify, including batch versions for efficiency. The count is justified given the breadth of Spotify's API, though it could be slightly trimmed.
The tool set covers nearly all read operations for Spotify entities, including batch fetches, charts, visuals, lyrics, and events. Missing are recommendation endpoints and playlist creation/modification, but for a scraper this is acceptable.