spotify-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOTIFY_CLIENT_ID | No | Client ID from Spotify Developer Dashboard | |
| SPOTIFY_ACCESS_TOKEN | No | Access token obtained after authentication | |
| SPOTIFY_CLIENT_SECRET | No | Client Secret from Spotify Developer Dashboard | |
| SPOTIFY_REFRESH_TOKEN | No | Refresh token obtained after authentication |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spotify_health_checkB | Check if the Spotify MCP server is authenticated and operational |
| spotify_get_auth_statusA | Get authentication status and instructions for setting up Spotify credentials |
| spotify_setup_instructionsA | Get detailed setup instructions for authenticating the Spotify MCP server |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
All three tools — get_auth_status, health_check, and setup_instructions — serve nearly identical purposes related to authentication and server status. An agent would struggle to select the correct tool because they all provide information about setup or health with no distinct functional boundaries.
All tools use snake_case with a 'spotify_' prefix, but the naming pattern is inconsistent: 'get_auth_status' follows a verb_noun pattern, while 'health_check' and 'setup_instructions' are noun_noun combinations, breaking the expected consistency.
With only 3 tools, all dedicated to authentication and health, the server is vastly undersized for a Spotify service, which would typically require many tools for playback, search, queue management, etc. The count is far too low for the implied scope.
The tool surface covers only authentication and setup, missing core Spotify functionalities like play, pause, search, and playlist management. This is a severe gap that renders the server unable to perform any music-related tasks.