astra-mcp
Related Servers
Alternatives to astra-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP server for the Spotify Web API — gives Claude and other AI assistants tools to search music, control playback, manage playlists, library, and podcasts.59MIT
- AlicenseAqualityBmaintenanceMCP server to control Spotify conversationally from Claude, Cursor, and other AI clients.1186 npmMIT
- FlicenseAqualityDmaintenanceA 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.412-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets Claude search the Beatport catalog and manage your Beatport playlists, including adding tracks to playlists by name.MIT
- 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-
- AlicenseBqualityDmaintenanceMCP server that provides LLM tools to interact with Lyrion Music Server (LMS), enabling player control, playback management, playlist operations, and music library search.557 npmMIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action: search returns refs, play/enqueue/queue_edit manage the queue, control handles transport, set_favorite toggles favorites, playlist manages playlists, open navigates the UI, and now_playing/capabilities are informational. There is minor potential overlap between astra_play and astra_control 'play', but descriptions clearly separate starting a specific item from resuming playback.
All tools share the astro_ prefix, but the pattern is not uniform: most are verb_noun (set_favorite, queue_edit) or bare verbs (open, play, search), while some are nouns (queue, capabilities, playlist) implying a 'get' action. Occasional phrases like now_playing deviate from a strict verb_noun convention, but the prefix and readable structure keep it mostly consistent.
With 11 tools, the server is well-scoped for a music player control surface. Each tool covers a distinct operation without redundancy, and the count is within the ideal range for a focused MCP server.
The core workflows are covered: search, play, control, queue management, favorite toggling, and playlist CRUD (minus deletion, which is documented as unavailable). Minor gaps exist: there is no tool to list favorites or fetch the contents of a playlist, and search is bounded without pagination, but agents can work around these via now_playing/queue for current state and by using playlist refs directly.