mcp-spotify-cli
Related Servers
Alternatives to mcp-spotify-cli
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Spotify that enables playlist building and music discovery through 19 tools, allowing LLM agents to search tracks/artists/albums, manage playlists, control playback, and access personal listening data.2041 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceA robust MCP server that connects Spotify playback, search, and library management to LLM agents via tools, with dual authentication and reliable token handling.2MIT
- FlicenseNot gradedqualityDmaintenanceDual-mode tool server for controlling Spotify through terminal or AI assistants like Claude or ChatGPT.-
- AlicenseBqualityCmaintenanceA lightweight Model Context Protocol server that enables AI assistants like Cursor & Claude to control Spotify playback and manage playlists.22490MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables controlling Spotify playback through natural language commands in MCP clients like Cursor or Claude for Desktop.1-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude Desktop to interact with Spotify's music streaming service, supporting playback control, playlist management, music search, and user profile access.412MIT
TDQS
Scored across 12 tools
Each tool targets a distinct resource or playback action: playback state, devices, track search, playlist search, user playlists, and specific playback controls. There is no meaningful overlap between search_track/search_playlist or between play/pause/next/previous.
Names are consistently snake_case and mostly follow verb_noun or action_noun patterns (get_current_track, list_devices, set_volume). Minor deviations exist with bare verbs play/pause and next_track/previous_track, but the set remains predictable.
Twelve tools is well-scoped for Spotify playback control, with each tool covering a distinct operation. The count is neither thin nor excessive for the domain.
Core playback is covered: play, pause, skip, volume, shuffle, repeat, current track, search, and playlists. However, notable gaps remain: no device transfer/selection despite list_devices, no seek/position control, no queue management, and no playback state beyond the current track.