Most people will want the hosted server — a URL, an OAuth login, done. The CLI matters for the other case: `--json` on every command means an agent can chain search into playlist-building through jq, and tokens refresh automatically so non-interactive runs keep working after the first `auth`. Adding a whole album to a playlist in one call is the kind of small thing that saves a loop.
A wrapper around the Tidal API v2, shipped two ways: a command-line tool where every command takes `--json`, and a remote MCP server for Claude Desktop and other clients.
- 40 tools over the remote server, with OAuth authentication, safety annotations and 3 prompt templates
- Search across artists, albums, tracks, videos and playlists, plus autocomplete suggestions and editorial search
- Artists — info, top tracks, discography, similar artists and radio; albums by ID or barcode; tracks by ID, ISRC, similar or radio
- Playlists get full CRUD: create, rename, set description, delete, add and remove tracks, reorder, and add an entire album at once
- Library favourites for artists, albums, tracks, videos and playlists
- Recommendations — Daily, Discovery, New Release and Offline mixes — with drill-down into the items inside a mix
- History for recently added tracks, albums and artists, plus search history you can list, delete or clear
- Save for Later as a separate queue from your library; share links for tracks and albums
- Playback: stream info, direct URLs and local playback, with LOW, HIGH, LOSSLESS and HI_RES quality options
For the remote server, nothing local: add https://tidal-cli.lucaperret.ch/api/mcp as a custom connector and log in to Tidal. For the CLI, `npm install -g @lucaperret/tidal-cli` with Node.js 20 or newer, then `tidal-cli auth` once — it opens your browser. A Tidal account either way. It is also published as an OpenClaw skill on ClawHub.
One command — npm install -g @lucaperret/tidal-cli