A
licenseA
qualityB
maintenanceMCP server to control Spotify conversationally from Claude, Cursor, and other AI clients.
11
86 npm
MIT
spotify-llm-mcp
by rachittshah
Related Servers
Alternatives to spotify-llm-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables control of Spotify playback, search, and playlist management through MCP tools and Apple Shortcuts/Siri integration via HTTP bridge.12-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search Spotify and manage playlists, library, and playback via a remote MCP server running on Cloudflare Workers.45 npm1MIT
- AlicenseNot gradedqualityAmaintenanceExposes Spotify search, playlist, library, discovery, and playback tools to AI assistants over MCP Streamable HTTP. Supports Spotify OAuth, multi-client MCP OAuth with PKCE and dynamic client registration, encrypted token storage, and self-hosted Docker deployment.1AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables control of Spotify playback, track search, and user profile retrieval via MCP tools with automatic OAuth token management.45 npm3MIT
- AlicenseAqualityCmaintenanceEnables controlling a Lyrion Music Server through MCP tools for playback control, library search, and queue management.127 npmMIT
TDQS
A3.6/5.0
Scored across 14 tools
Disambiguation4/5
Most tools have a clear resource+action distinction, but search, play, and resolve_tracks overlap in their underlying lookup/resolution behavior, and the playlist creation/append tools both resolve track picks. Descriptions are usually enough to pick the right one.
Naming Consistency3/5
Names are mostly readable but inconsistent: verb_noun forms like play_playlist and list_devices coexist with bare verbs like play and control, plus noun phrases like now_playing and taste_profile. The generic name control is particularly vague.
Tool Count4/5
14 tools is a reasonable size for a Spotify assistant covering playback, queue, devices, search, and playlist management. Some search/resolve and playback-control functionality could be consolidated, but the count is not excessive.
Completeness3/5
Core workflows are covered: playback control, queue, devices, search, taste profile, and creating/appending playlists. However, there is no way to remove tracks or delete/replace playlists, nor any queue editing or recommendation tool, leaving notable playlist-lifecycle gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues