Tidal Mcp

io.github.ibealPublished by GitHub account ibealv0.6.0Updated Oct 24, 2026

MCP server for TIDAL - search tracks, manage playlists, and get personalized recommendations

VerifiedSTDIODesktop onlyProductivity & WorkflowMedia & Design

Overview

AI-generated overview

A local MCP server for TIDAL that lets an assistant search music, read favorites and playlists, get recommendations, and create or edit playlists in your TIDAL.

What you can do
Search TIDAL for tracks, albums, artists and playlists, or run a combined search across all content types. Read your favorite tracks and list your playlists, fetching every track in a playlist with automatic pagination. Get personalized track recommendations based on your listening history plus criteria you give. Create, delete, rename or re-describe playlists. Add, remove and reorder tracks within a playlist. Authenticate with TIDAL through a browser login flow.
When to use it
Useful when you want an assistant to curate TIDAL playlists from your own tastes and criteria, for example finding tracks similar to your recent favorites or building a themed playlist from your top tracks. It suits people who already use TIDAL and want conversational playlist building rather than the platform's built-in recommendations.
Requirements
Runs locally as a stdio process, via Docker (image ghcr.io/ibeal/tidal-mcp) or a Python 3.10+ install with uv. Needs a TIDAL subscription and a one-time OAuth browser login; the session is saved to a file (for example /tmp/tidal-session-oauth.json). The TIDAL_MCP_PORT environment variable sets the local API port (default 5050). Docker setups mount /tmp and use host networking.
Before you install
The assistant can change your TIDAL account: it can create and delete playlists and add, remove or reorder tracks, and the README notes it may delete a playlist on request. The saved OAuth session file grants access to your account, so keep it private. Docker configuration mounts the host /tmp directory and uses host networking, which widens what the container can reach.

Installation

In SourceWeft

  1. Open Tidal Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

🎵 TIDAL MCP (Community Maintained Fork)

📢 Active Maintenance Notice: This is an actively maintained community fork of yuhuacheng/tidal-mcp. The original repository appears unmaintained since May 2025. Contributions, issues, and PRs are welcome here!

[Active Development] [Docker Support] [Python 3.10+] [MCP Compatible]

[Demo: Music Recommendations in Action]

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.

With TIDAL MCP, you can ask for things like:

"Based on my last 10 favorites, find similar tracks — but only ones from recent years."

"Find me tracks like those in this playlist, but slower and more acoustic."

The LLM filters and curates results using your input, finds similar tracks via TIDAL's API, and builds new playlists directly in your account.

🆕 What's New in This Fork

This community fork includes significant improvements over the original:

  • ✅ Docker Support: Full Docker and docker-compose setup for easy deployment
  • ✅ Search Functionality: Search for tracks, albums, artists, and playlists across TIDAL
  • ✅ Pagination: Fetch all tracks from large playlists (no more 50-track limit!)
  • ✅ Complete Playlist Editing: Add, remove, reorder tracks, and update metadata
  • ✅ Refactored Codebase: ~60% smaller files with better organization and maintainability
  • ✅ DRY Pagination Helper: Reusable pagination utilities across all endpoints

See the full changelog and contribute at: https://github.com/ibeal/tidal-mcp

Features

  • 🌟 Music Recommendations: Get personalized track recommendations based on your listening history plus your custom criteria
  • 🎵 Full Playlist Management: Create, view, edit, and delete playlists with complete control
  • 🔍 Advanced Search: Search across tracks, albums, artists, and playlists
  • 📄 Smart Pagination: Automatically fetch all tracks from playlists of any size
  • 🎛️ Playlist Editing: Add, remove, reorder tracks, and update metadata
  • 🐳 Docker Ready: Easy deployment with Docker and docker-compose support
  • 🔐 OAuth Authentication: Secure browser-based TIDAL login flow

Quick Start

Prerequisites

  • Python 3.10+ OR Docker
  • uv (Python package manager) - only needed for non-Docker installation
  • TIDAL subscription

Installation

Option 1: Docker (Recommended)
  1. Clone this repository:

    bash
    git clone https://github.com/ibeal/tidal-mcp.gitcd tidal-mcp
  2. Build and run with Docker Compose:

    bash
    docker-compose up -d

    Or with Docker directly:

    bash
    docker build -t tidal-mcp .docker run -d -p 5050:5050 --name tidal-mcp tidal-mcp

    The server will be available at http://localhost:5050.

  3. To customize the port, edit the TIDAL_MCP_PORT environment variable in docker-compose.yml or pass it to docker run:

    bash
    docker run -d -p 5100:5100 -e TIDAL_MCP_PORT=5100 --name tidal-mcp tidal-mcp
Option 2: Local Python Installation
  1. Clone this repository:

    bash
    git clone https://github.com/ibeal/tidal-mcp.gitcd tidal-mcp
  2. Create a virtual environment and install dependencies using uv:

    bash
    uv venvsource .venv/bin/activate  # On Windows: .venv\Scripts\activate
  3. Install the package with all dependencies from the pyproject.toml file:

    bash
    uv pip install --editable .

    This will install all dependencies defined in the pyproject.toml file and set up the project in development mode.

MCP Client Configuration

Claude Desktop Configuration

To add this MCP server to Claude Desktop, you need to update the MCP configuration file.

Option 1: Docker Configuration (if using Docker)
json
{  "mcpServers": {    "TIDAL Integration": {      "command": "docker",      "args": [        "run",        "--rm",        "-i",        "--network",        "host",        "-v",        "/tmp:/tmp",        "tidal-mcp"      ],      "env": {        "TIDAL_MCP_PORT": "5050"      }    }  }}

Setup:

  1. Build the Docker image:

    bash
    docker build -t tidal-mcp .
  2. Authenticate with TIDAL (run this once):

    bash
    docker-compose -f docker-compose.auth.yml run --rm tidal-auth

    You'll see the OAuth URL in the output:

    ============================================================TIDAL LOGIN REQUIREDPlease open this URL in your browser:
    https://link.tidal.com/XXXXX
    Expires in 300 seconds============================================================

    Open the URL in your browser, log in to TIDAL, and the session will be saved to /tmp/tidal-session-oauth.json.

  3. Update your Claude Desktop config (see above) and restart Claude Desktop.

Configuration details:

  • --network host - Allows the container to use the host's network directly
  • -v /tmp:/tmp - Mounts the host's /tmp directory so the TIDAL session persists across container restarts

To use a custom port:

json
{  "mcpServers": {    "TIDAL Integration": {      "command": "docker",      "args": [        "run",        "--rm",        "-i",        "--network",        "host",        "-v",        "/tmp:/tmp",        "-e",        "TIDAL_MCP_PORT=5100",        "tidal-mcp"      ]    }  }}
Option 2: Local Python Configuration (if not using Docker)
json
{  "mcpServers": {    "TIDAL Integration": {      "command": "/path/to/your/uv",      "env": {        "TIDAL_MCP_PORT": "5100"      },      "args": [        "run",        "--with",        "requests",        "--with",        "mcp[cli]",        "--with",        "flask",        "--with",        "tidalapi",        "mcp",        "run",        "/path/to/your/project/tidal-mcp/mcp_server/server.py"      ]    }  }}

Example scrrenshot of the MCP configuration in Claude Desktop: [Claude MCP Configuration]

Cursor Configuration

For Cursor users, add this configuration to your MCP settings file (~/.cursor/mcp.json):

json
{  "mcpServers": {    "TIDAL Integration": {      "command": "/path/to/your/project/tidal-mcp/.venv/bin/python",      "env": {        "TIDAL_MCP_PORT": "5100"      },      "args": ["/path/to/your/project/tidal-mcp/start_mcp.py"]    }  }}

Important: Replace /path/to/your/project/tidal-mcp with the actual path to your project directory.

Steps to Install MCP Configuration in Cursor
  1. Create or edit the MCP configuration file at ~/.cursor/mcp.json
  2. Add the TIDAL Integration configuration above
  3. Update the paths to match your actual project location
  4. Save the file
  5. Restart Cursor to load the new MCP server

Steps to Install MCP Configuration in Claude Desktop

  1. Open Claude Desktop
  2. Go to Settings > Developer
  3. Click on "Edit Config"
  4. Paste the modified JSON configuration
  5. Save the configuration
  6. Restart Claude Desktop

Suggested Prompt Starters

Once configured, you can interact with your TIDAL account through a LLM by asking questions like:

  • “Recommend songs like those in this playlist, but slower and more acoustic.”
  • “Create a playlist based on my top tracks, but focused on chill, late-night vibes.”
  • “Find songs like these in playlist XYZ but in languages other than English.”

💡 You can also ask the model to:

  • Use more tracks as seeds to broaden the inspiration.
  • Return more recommendations if you want a longer playlist.
  • Or delete a playlist if you’re not into it — no pressure!

Available Tools

The TIDAL MCP integration provides the following tools:

Authentication & Core Features

  • tidal_login: Authenticate with TIDAL through browser login flow
  • get_favorite_tracks: Retrieve your favorite tracks from TIDAL
  • recommend_tracks: Get personalized music recommendations

Playlist Management

  • 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 (with automatic pagination)
  • delete_tidal_playlist: Delete a playlist from your TIDAL account
  • add_tracks_to_playlist: Add tracks to an existing playlist
  • remove_tracks_from_playlist: Remove tracks by ID or position index
  • update_playlist_metadata: Update playlist title and/or description
  • reorder_playlist_tracks: Move tracks to different positions within a playlist

Search & Discovery

  • search_tidal: Comprehensive search across all TIDAL content types
  • search_tracks: Search specifically for tracks/songs
  • search_albums: Search specifically for albums
  • search_artists: Search specifically for artists
  • search_playlists: Search specifically for playlists

License

MIT License

Contributing

This is an actively maintained community fork. Contributions are welcome!

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Acknowledgements

Original Project:

Contributors:

  • ra100 - Search functionality features

Libraries & Frameworks:

Source: README.md at commit bf086bb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.6.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts