Skip to main content
Glama
fborello

MCP Spotify Server

by fborello

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPOTIFY_CLIENT_IDYesYour Spotify Client ID from the Spotify Developer Dashboard
SPOTIFY_REDIRECT_URINoThe redirect URI configured in your Spotify app settingshttp://localhost:3000/callback
SPOTIFY_CLIENT_SECRETYesYour Spotify 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
spotify_authB

Inicia o processo de autenticação com o Spotify

spotify_set_tokensC

Conclui a autenticação com o código recebido do Spotify

spotify_searchC

Busca por músicas, artistas, álbuns ou playlists no Spotify

spotify_playC

Toca uma música específica no Spotify

spotify_pauseC

Pausa a reprodução atual

spotify_resumeC

Retoma a reprodução pausada

spotify_nextC

Pula para a próxima música

spotify_previousB

Volta para a música anterior

spotify_current_playingB

Obtém informações sobre a música que está tocando

spotify_devicesB

Lista dispositivos disponíveis para reprodução

spotify_playlistsC

Lista playlists do usuário

spotify_play_playlistC

Toca uma playlist específica

spotify_create_playlistC

Cria uma nova playlist no Spotify

spotify_add_tracks_to_playlistC

Adiciona músicas a uma playlist existente

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 14 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: authentication (auth, set_tokens), playback control (play, pause, resume, next, previous), playlist management (create, add_tracks, playlists, play_playlist), search, and device/status queries. The descriptions reinforce these distinct roles, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent 'spotify_verb' or 'spotify_verb_noun' pattern in snake_case, with verbs like 'add', 'create', 'play', 'pause', etc. This predictability makes the tool set easy to navigate and understand at a glance.

Tool Count5/5

With 14 tools, this server is well-scoped for a Spotify integration, covering authentication, playback control, playlist operations, search, and device management. Each tool earns its place without bloat, supporting common user workflows effectively.

Completeness4/5

The tool surface is nearly complete for core Spotify interactions, including authentication, playback, playlists, and search. A minor gap is the lack of tools for modifying or deleting playlists, but agents can work around this with existing tools like create and add_tracks.

Maintenance

ActivityInactive
ResponsivenessNo issues