Skip to main content
Glama
Spotify Data MCP Server

Spotify Data MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPOTIFY_API_KEYYesYour Spotify Data API key. Required.
SPOTIFY_API_BASENoOverride the base URL of the chosen provider.
SPOTIFY_API_PROVIDERNoThe API provider: 'rapidapi' (RapidAPI spotify81.p.rapidapi.com) or 'direct' (https://spotify-proxy.checkleaked.cc/spotify-data). Default: detected from the key.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Read-only Spotify catalog data from the CheckLeaked Spotify Data API: track play counts, artist monthly listeners, followers, world rank and top cities, Top 200 and viral charts, search, albums, playlists, ISRC lookup, and genres / moods / BPM.

  • Every tool accepts Spotify ids, spotify: URIs and open.spotify.com URLs. With only a name, call search first to get the id.

  • Each call spends one request of the user's API key (get_playlist spends two on its first page), so pass up to 50 ids in one call instead of one call per item.

  • Spotify shows a play count of 0 for tracks with fewer than 1,000 plays.

  • Unofficial: not affiliated with or endorsed by Spotify.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Search the Spotify catalog by name to find ids for the other tools. type picks what to search: tracks, artists, albums or playlists. Returns up to limit hits (max 20) with id, name, key fields and open.spotify.com URL. For track searches, include_play_counts adds each hit's lifetime play count.

get_tracksA

Track details for up to 50 tracks in one call: name, artists, album, release date, duration, explicit flag, popularity, ISRC and (by default) lifetime play count. include_insights adds genres, moods, activities, BPM, credits, lyrics flag and languages. A play count of 0 means fewer than 1,000 plays.

get_track_play_countA

Lifetime Spotify play counts (streams) for up to 50 tracks in one call, with track name, artists and release date. The fastest way to compare streams. A play count of 0 means fewer than 1,000 plays.

get_track_insightsB

Genres, moods and activities (with Spotify's 0-1 weights), tempo in BPM, credits (writers, producers), lyrics flag and vocal languages for up to 50 tracks.

get_artists_statsB

Monthly listeners, followers, world rank, popularity, genres and top 5 cities (with listener counts) for up to 50 artists in one call.

get_artist_overviewB

One artist's profile: monthly listeners, followers, world rank, top cities, top tracks with play counts, latest release, discography counts, related artists, biography and social links.

get_artist_insightsA

An artist's sound profile from their top tracks: genres, moods and activities with 0-1 weights, and tempo (average, min, max BPM). Up to 20 artists per call.

get_related_artistsB

Artists Spotify lists as related to ("Fans also like") the given artist.

get_albumB

An album with its track list and (by default) every track's lifetime play count, plus the album total, release date, label, UPC and popularity.

get_playlistA

A playlist's name, owner, followers and description, plus limit tracks (max 100) from offset with lifetime play counts. Use next_offset from the answer to page through long playlists (later pages skip the metadata and cost one request).

get_chartA

Spotify Charts by country: top_tracks (Top 200), viral_tracks (Viral 50, daily only), top_artists or top_albums. Each entry has rank, previous and peak rank, days (or weeks) on the chart, movement and, for top_tracks, the streams in that period. Defaults to the latest published daily chart.

isrc_lookupA

Find the Spotify track(s) for an ISRC (International Standard Recording Code), e.g. USUG11904206. Returns ids, names, artists, album and release date.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 12 tools

Disambiguation3/5

The track tools overlap heavily: get_tracks already returns play counts by default and insights via include_insights, which largely subsumes get_track_play_count and get_track_insights. Similarly get_artist_overview absorbs much of get_artists_stats and get_artist_insights. Descriptions do help (batch vs. single, 'fastest way to compare streams'), but an agent still has to reason about which of several near-duplicate paths to take.

Naming Consistency4/5

Most tools follow a clear get_<resource> pattern (get_tracks, get_album, get_playlist, get_chart), with two outliers: 'search' (bare verb, no noun) and 'isrc_lookup' (noun_verb reversed). Singular/plural switching (get_tracks vs. get_track_play_count) is slightly irregular but readable and intentional.

Tool Count5/5

Twelve tools is well within the sweet spot and each maps to a concrete Spotify data concept (tracks, artists, albums, playlists, charts, ISRC). Nothing feels padded except arguably the redundant track/artist variants, but the count itself is well scoped.

Completeness4/5

The surface covers the analytics domain well: discovery via search and isrc_lookup, batch and single lookups across tracks/artists/albums/playlists, plus charts. Minor gaps remain — albums are single-only with no batch counterpart, and there is no way to list an artist's full discography or enumerate playlists, but these are workaroundable.

Maintenance

ActivityNo data
ResponsivenessOutdated data