TIDAL MCP
Related Servers
Alternatives to TIDAL MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables highly personalized music recommendations from TIDAL based on custom criteria, allowing users to create and manage playlists directly in their TIDAL account.7MIT
- FlicenseNot gradedqualityDmaintenanceA full-featured YouTube Music MCP server that lets AI assistants control playback, browse history, download songs, and manage playlists via natural language.1-
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server that enables AI assistants to control music playback, manage users and access, configure providers, and administer a Music Assistant setup through natural language commands.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Apple Music that lets AI assistants manage playlists, control playback, and browse the music library.108MIT
- AlicenseNot gradedqualityDmaintenanceAI-native MCP server for Qobuz that enables searching, browsing, and managing your music library, including favorites, playlists, and current playback.50 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn unofficial MCP server that provides access to Spotify's Web API through the Model Context Protocol, enabling AI assistants to search music, manage playlists, and control playback.12 npm9ISC
TDQS
Scored across 19 tools
Most tools have distinct resource-action boundaries (playlist CRUD, mixes, favorites, recommendations, auth). However, search_tidal overlaps with the four type-specific search tools, which could cause an agent to pick the wrong search tool despite clear descriptions.
The set mostly follows a verb_noun pattern with clear families like get_*, search_*, and *_playlist. Minor exceptions include tidal_login breaking the verb-first pattern and create_tidal_playlist including 'tidal' while other playlist tools do not.
19 tools is on the higher end but reasonable for a music service covering authentication, search, playlist management, mixes, history, and recommendations. Each tool addresses a distinct operation, so the count feels justified rather than bloated.
The playlist lifecycle is well covered with create, read, update, delete, add, remove, and reorder operations, plus favorites, mixes, history, search, and recommendations. Minor gaps like adding/removing favorite tracks or fetching individual track/album details are workable but not fatal.