Spotify-Claude MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Name | Description |
|---|---|
| get_artistD | Get Artist name |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_artist' has a clear, distinct purpose that cannot be confused with any other tool in this set.
The naming follows a consistent verb_noun pattern with 'get_artist'. With only one tool, there is no inconsistency to evaluate, and the naming convention is clear and appropriate for the tool's function.
A single tool is too few for a server named 'Spotify-Claude MCP Server', which suggests a broader music or artist domain. This minimal toolset severely limits functionality and does not provide adequate coverage for typical Spotify-related tasks like searching, playing, or managing playlists.
The tool surface is severely incomplete for a Spotify server. It only allows getting an artist name, with no support for other core operations such as searching for tracks, playing music, managing playlists, or accessing album information, making it impractical for most agent workflows.