TIDAL MCP
# π΅ TIDAL MCP (Community Maintained Fork)
> **π’ Active Maintenance Notice**: This is an actively maintained community fork of [yuhuacheng/tidal-mcp](https://github.com/yuhuacheng/tidal-mcp).
> The original repository appears unmaintained since May 2025. **Contributions, issues, and PRs are welcome here!**
[](https://github.com/ibeal/tidal-mcp)
[](https://github.com/ibeal/tidal-mcp#option-1-docker-recommended)
[](https://www.python.org/downloads/)
[](https://modelcontextprotocol.io)

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](https://github.com/astral-sh/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.git
cd 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.git
cd tidal-mcp
```
2. Create a virtual environment and install dependencies using uv:
```bash
uv venv
source .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 REQUIRED
Please 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:

### 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](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:**
- [yuhuacheng/tidal-mcp](https://github.com/yuhuacheng/tidal-mcp) - Original TIDAL MCP implementation
**Contributors:**
- [ra100](https://github.com/ra100) - Search functionality features
**Libraries & Frameworks:**
- [Model Context Protocol (MCP)](https://github.com/modelcontextprotocol/python-sdk)
- [TIDAL Python API](https://github.com/tamland/python-tidal)
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.