Tidal Cli MCP Server

CLI for Tidal music streaming service, designed for LLM agent automation

Local serverstdio

What is the Tidal Cli MCP server?

Tidal Cli MCP server exists for a simple reason — assistants are far more useful when they can act on Tidal Cli directly instead of describing what you should do. CLI for Tidal music streaming service, designed for LLM agent automation.

What you get

40 tools with OAuth authentication, safety annotations, and 3 prompt templates.

  • Search — artists, albums, tracks, videos, playlists, and autocomplete suggestions
  • Artists — — info, top tracks, discography, similar artists, radio
  • Albums — — details, barcode lookup
  • Tracks — — info, similar tracks, ISRC lookup, radio
  • Playlists — — full CRUD, add/remove tracks, reorder, add entire albums
  • Library — — favorites for artists, albums, tracks, videos, playlists

Setting it up

The server ships on npm as @lucaperret/tidal-cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Tidal Cli is connected, these are the calls the assistant has available:

  • Requirements — The Requirements tool exposed by this server
  • Search — The Search tool exposed by this server
  • Artist — The Artist tool exposed by this server
  • Playlists — The Playlists tool exposed by this server
  • Library — The Library tool exposed by this server
  • Playback — The Playback tool exposed by this server

Configuration and credentials

  • Node.js >= 20 - A Tidal account

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the tidal cli mcp server does with a few real requests.

Choosing this one

This sits in the AI and media services group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Tidal Cli's toolset — Requirements, Search, Artist and 3 more — is a fair guide to whether it matches your workflow. It is maintained by lucaperret; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Tidal Cli's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
RequirementsThe Requirements tool exposed by this server.
SearchThe Search tool exposed by this server.
ArtistThe Artist tool exposed by this server.
PlaylistsThe Playlists tool exposed by this server.
LibraryThe Library tool exposed by this server.
PlaybackThe Playback tool exposed by this server.

How to install the Tidal Cli MCP server

{
  "mcpServers": {
    "tidal-cli": {
      "command": "npx",
      "args": ["-y", "@lucaperret/tidal-cli"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js >= 20 - A Tidal account

Example prompts to try

  • Use Tidal Cli to Requirements.
  • Use Tidal Cli to Search.
  • Use Tidal Cli to Artist.

Frequently asked questions

It connects Tidal Cli to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Requirements, Search, Artist, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Tidal Cli directly.