Tidal MCP Server

Tidal mcp mcp server connects Tidal MCP to AI assistants that speak the Model Context Protocol. Most music platforms offer recommendations — Daily Discovery, Top Artists, New Arrivals, etc. — but even with the state-of-the-art system, they often feel too "aggregated". I wanted something more custom and context-aware.

What Tidal MCP does

Most music platforms offer recommendations — Daily Discovery, Top Artists, New Arrivals, etc. — but even with the state-of-the-art system, they often feel too "aggregated". I wanted something more custom and context-aware.

Key capabilities

• 🌟 Music Recommendations: Get personalized track recommendations based on your listening history plus your custom criteria
• ၊၊||၊ Playlist Management: Create, view, and manage your TIDAL playlists

Tools it exposes

Once connected, the assistant can call these 9 tools directly:

• tidal_login — Authenticate with TIDAL through browser login flow
• get_favorite_tracks — Retrieve your favorite tracks from TIDAL
• recommend_tracks — Get personalized music recommendations
• create_tidal_playlist — Create a new playlist in your TIDAL account
• get_user_playlists — List all your playlists on TIDAL
• get_playlist_tracks — Retrieve all tracks from a specific playlist
• delete_tidal_playlist — Delete a playlist from your TIDAL account
• Prerequisites — The Prerequisites tool exposed by this server
• Installation — 1. Clone this repository: bash git clone https://github.com/yuhuacheng/tidal-mcp.git cd tidal-mcp

Installing the tidal mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

The server reads one environment variable: TIDAL_MCP_PORT. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Python 3.10+ - uv (Python package manager) - TIDAL subscription

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Tidal MCP sits in that group, and the shape of its toolset — tidal_login, get_favorite_tracks, recommend_tracks among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• With 9 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Tidal MCP.
• Maintained by yuhuacheng, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the tidal mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.