Skip to main content
Glama
ashwanth1109

Spotify MCP

by ashwanth1109
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPOTIFY_CLIENT_IDYesYour Spotify API client ID from the Spotify Developer Dashboard
SPOTIFY_REDIRECT_URIYesThe redirect URI configured in your Spotify Developer Dashboard
SPOTIFY_CLIENT_SECRETYesYour Spotify API client secret from the Spotify Developer Dashboard

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_my_playlistsC

FastMCP tool to get user playlists using SpotifyClient.

start_playbackB

FastMCP tool to resume playback on the currently active Spotify device.

pause_playbackB

FastMCP tool to pause playback on spotify.

search_spotifyC
Search Spotify for tracks, artists, albums, or playlists.
Args:
    query: Search term
    type: One of 'track', 'artist', 'album', 'playlist'
    limit: Max number of results
next_trackA

Skip to next track in queue

previous_trackB

Go back to previous track

seek_positionC
Seek to position in current track
Args:
    position_ms: Position in milliseconds
get_playback_stateB

Get current playback information

get_recommendationsB
Get Spotify recommendations based on seeds
Args:
    seed_artists: Comma-separated artist IDs
    seed_tracks: Comma-separated track IDs
    seed_genres: Comma-separated genres
    limit: Number of recommendations
get_item_infoC
Get detailed information about a Spotify item
Args:
    item_id: Spotify ID
    type: One of 'track', 'album', 'artist', 'playlist'
start_playback_trackC
Start playback of a specific track on Spotify
Args:
    track_uri: Spotify URI of the track (e.g. 'spotify:track:1234...')
    device_id: Optional device to play on
get_top_artistsB
Get user's top artists from Spotify
Args:
    limit: Number of artists (max 50)
    time_range: One of 'short_term' (4 weeks), 'medium_term' (6 months), 'long_term' (all time)
get_queueB

Get the current queue of tracks

add_to_queueC
Add a track to the queue
Args:
    track_id: Spotify track ID to add
skip_tracksC
Skip multiple tracks at once
Args:
    num_skips: Number of tracks to skip (default: 1)
get_current_trackB

Get information about the currently playing track

start_playlist_playbackC
Start playback of a specific playlist
Args:
    playlist_id: Spotify playlist ID
    device_id: Optional device to play on
get_artist_top_tracksC
Get top tracks for an artist
Args:
    artist_id: Spotify artist ID
set_repeat_modeB
Set repeat mode for playback
Args:
    state: One of 'track', 'context', or 'off'
add_to_playlistC
Add tracks to a playlist
Args:
    playlist_id: Spotify playlist ID
    track_ids: List of track IDs to add
reorder_queueB
Reorder tracks in queue by moving a track to a different position
Args:
    range_start: Position of track to move
    insert_before: Position to insert the track

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.2/5.0

Scored across 21 tools

Disambiguation4/5

Most tools have distinct purposes targeting specific Spotify resources and actions, with clear boundaries between playback control, queue management, and content retrieval. However, some overlap exists between 'skip_tracks' and 'next_track'/'previous_track', and 'start_playback' vs 'start_playback_track'/'start_playlist_playback' could cause confusion about which to use for resuming vs starting specific content.

Naming Consistency4/5

The server maintains strong consistency with snake_case naming throughout and mostly follows verb_noun patterns (e.g., 'get_current_track', 'add_to_queue', 'search_spotify'). Minor deviations include 'get_item_info' (noun_verb) and some tools using 'playback' while others use 'track'/'playlist' in similar contexts, but the overall pattern remains clear and predictable.

Tool Count3/5

With 21 tools, this feels borderline heavy for a music streaming interface. While Spotify's API is feature-rich, the tool set includes some redundancy (e.g., multiple skip/playback variants) that could potentially be consolidated. The count is manageable but approaches the upper limit of what feels well-scoped for this domain.

Completeness5/5

The tool surface provides comprehensive coverage of Spotify's core functionality including playback control (play/pause/skip/seek/repeat), queue management, content retrieval (tracks/artists/playlists/recommendations), search capabilities, and user data access. There are no obvious gaps for typical agent workflows, with CRUD-like operations well-represented across the music streaming domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources