tidal-mcp
Integrates with the official TIDAL API to search the catalog, look up similar tracks, and manage TIDAL playlists, including creating playlists, adding or removing tracks, updating playlist details, and deleting playlists.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
tidal-mcp
An MCP server that lets ChatGPT, Claude, or any MCP client build and manage your TIDAL playlists.
"Make me a 25-song playlist of late-90s neo-soul, skip anything over 6 minutes."
It talks to the official TIDAL API with your own developer app. It does not use reverse-engineered endpoints or a shared client id, so a TIDAL app update won't break it.
Run it two ways:
Remote, on Cloudflare Workers (free plan). You get an HTTPS URL for ChatGPT, Claude.ai, or anything else that needs one. Always on.
Local, over stdio. For Claude Code, Claude Desktop, Codex, and other clients that launch a local command.
Tools
Tool | What it does |
| Search the catalog for tracks |
| Turn a list of "Artist - Title" strings into track ids in one call |
| Tracks TIDAL considers similar to a given track |
| Your playlists, most recently changed first |
| A playlist's details and tracks |
| Create a playlist, optionally filled with tracks |
| Append tracks (skips duplicates by default) |
| Remove tracks from a playlist |
| Rename, re-describe, or change visibility |
| Delete a playlist (annotated as destructive, so clients ask first) |
Related MCP server: Spotify MCP Server
1. Create a TIDAL developer app
Go to the TIDAL Developer Dashboard, sign in, and create an app.
Under Settings → Edit, add your redirect URIs:
Remote:
https://<your-worker>.workers.dev/callback(you'll know the URL after the first deploy)Local:
http://127.0.0.1:8765/callback
Enable these scopes:
user.read,search.read,playlists.read,playlists.write,collection.readCopy the Client ID. No client secret is needed; sign-in uses PKCE.
2a. Remote: deploy to Cloudflare
You need Node 20+ and a free Cloudflare account.
git clone https://github.com/bigapejit/tidal-mcp.git
cd tidal-mcp
npm install
npx wrangler login
npx wrangler deploy # prints your workers.dev URL; creates the KV store
npx wrangler secret put TIDAL_CLIENT_ID # paste your client id
npx wrangler secret put ALLOWED_TIDAL_USER_IDS # optional: your TIDAL user id, so only you can connectAdd https://<your-worker>.workers.dev/callback to your TIDAL app's redirect URIs. Your MCP URL is https://<your-worker>.workers.dev/mcp.
To find your TIDAL user id, set ALLOWED_TIDAL_USER_IDS to 0, connect once, and read the id from the "isn't open to your TIDAL account" page. If you've used the local setup, node dist/cli.js status also prints it.
ChatGPT: Plugins → Add → Add custom MCP server. Paste the MCP URL, keep authentication on OAuth, and create it. ChatGPT sends you through a consent page and then TIDAL's own sign-in.
Claude.ai: Settings → Connectors → Add custom connector, then paste the MCP URL.
How it works: the Worker is an OAuth 2.1 authorization server for MCP clients (@cloudflare/workers-oauth-provider), and it signs you in through TIDAL. Your TIDAL tokens are stored only inside the encrypted grant in KV, and they refresh whenever the client refreshes its token. Requests are stateless, so no Durable Objects are needed, and normal use stays well inside the free plan.
2b. Local: run over stdio
git clone https://github.com/bigapejit/tidal-mcp.git
cd tidal-mcp
npm install # also builds
node dist/cli.js login --client-id YOUR_CLIENT_IDA browser opens to TIDAL's sign-in page. The session is saved to ~/.tidal-mcp/, readable only by your user, and refreshes automatically. Use --no-browser to print the URL instead, and --port if 8765 is taken (then register that redirect URI instead).
Then point your client at it, using the absolute path to dist/cli.js:
claude mcp add tidal -- node /absolute/path/to/tidal-mcp/dist/cli.js # Claude Code
codex mcp add tidal -- node /absolute/path/to/tidal-mcp/dist/cli.js # Codex{
"mcpServers": {
"tidal": { "command": "node", "args": ["/absolute/path/to/tidal-mcp/dist/cli.js"] }
}
}The JSON form is for Claude Desktop and other clients that use a config file.
node dist/cli.js Run the MCP server over stdio
node dist/cli.js login Sign in to TIDAL
node dist/cli.js status Check whether you're signed in
node dist/cli.js logout Delete the saved session and settingsTIDAL_CLIENT_ID, TIDAL_CLIENT_SECRET, and TIDAL_MCP_HOME (the session folder) can also be set as environment variables.
An unrelated package on npm is already named
tidal-mcp. Run this project from your clone as shown above, not withnpx tidal-mcp.
Notes
New playlists are unlisted unless you ask for a public one.
Search and availability follow your account's country.
Writes send an
Idempotency-Key, so a retried request never adds tracks twice.
Project layout
src/core/ TIDAL API client and MCP tools (runtime-neutral: fetch + Web Crypto)
src/node/ Local login flow and token storage
src/worker/ Cloudflare Worker: OAuth server, TIDAL sign-in, stateless MCP endpoint
src/cli.ts Local entry point (stdio server + login/status/logout)License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Remote streamable-HTTP MCP server running on a single Cloudflare Worker. Your assistant gets live Airbnb, Amazon, Booking.com, Google Flights, Maps and Reddit data, social search on X, Instagram and TikTok, the Meta Ad Library, and image/video generation without any keys. Connect your own accounts to let it send WhatsApp or Telegram messages, work an IMAP inbox, manage Meta Ads campaigns and publish to X and LinkedIn. OAuth 2.1 with PKCE; stored credentials are AES-256-GCM encrypted.
Real-time YouTube transcripts, comments, channels & video search MCP. Local npx or hosted OAuth.
Official Fibery MCP server: query and update your workspace from any AI client via OAuth.
Hosted remote MCP server for YNAB on Cloudflare Workers with OAuth
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables remote interaction with Spotify through the Model Context Protocol, allowing users to search tracks, control playback, and manage playlists with per-user OAuth authentication. It is hosted on Cloudflare Workers and supports remote MCP over HTTP for compatible clients.2-
- AlicenseAqualityBmaintenanceMCP server for the Spotify Web API — gives Claude and other AI assistants tools to search music, control playback, manage playlists, library, and podcasts.475MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search Spotify and manage playlists, library, and playback via a remote MCP server running on Cloudflare Workers.127 npm1MIT
- AlicenseNot gradedqualityBmaintenanceExposes Spotify search, playlist, library, discovery, and playback tools to AI assistants over MCP Streamable HTTP. Supports Spotify OAuth, multi-client MCP OAuth with PKCE and dynamic client registration, encrypted token storage, and self-hosted Docker deployment.1AGPL 3.0