MCP TIDAL 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tidal_loginA | Authenticate with TIDAL through browser login flow. This will open a browser window for you to log in to your TIDAL account. Returns: Authentication status message |
| check_authA | Check current TIDAL authentication status. Returns: Authentication status and user information |
| search_musicC | Search for music content on TIDAL. |
| get_trackA | Get detailed information about a specific track. |
| get_albumA | Get detailed information about a specific album. |
| get_artistC | Get detailed information about a specific artist. |
| get_user_playlistsA | Get the current user's playlists. Returns: List of user's playlists with URLs |
| get_playlist_tracksB | Get all tracks from a specific playlist. |
| get_favorite_tracksB | Get the current user's favorite tracks. |
| get_track_recommendationsB | Get recommended tracks based on a specific track. |
| create_playlistB | Create a new playlist in the user's account. |
| add_tracks_to_playlistB | Add tracks to an existing playlist. |
| remove_tracks_from_playlistB | Remove tracks from an existing playlist. |
| delete_playlistB | Delete a playlist from the user's account. |
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 14 tools
Each tool targets a distinct resource or action: authentication, search, album/artist/track retrieval, playlist CRUD, track management, favorites, and recommendations. There is no overlap, even between auth-related tools as one checks status and the other performs login.
Most tools follow a consistent verb_noun snake_case pattern (e.g., add_tracks_to_playlist, create_playlist, get_album). However, 'tidal_login' reverses the verb and noun order slightly, and 'check_auth' uses a shortened verb. Minor deviations but overall predictable.
With 14 tools, the server is well-scoped for a music streaming integration. It covers essential operations without redundancy, fitting comfortably within the ideal 3-15 range for a focused service.
The tool surface covers authentication, browsing, search, playlist management, favorites, and recommendations. Missing features like user profile retrieval or playback control could be considered minor gaps, but the core workflows are fully supported.