TIDAL Developer API MCP. Audit music catalogs, albums, and tracks with AI.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
The TIDAL Developer API lets your AI agent access high-fidelity music metadata directly. Use it to audit artist discographies, search for specific albums by title or artist, and retrieve detailed track lists, durations, and identifiers without logging into a separate streaming app.
What your AI agents can do
Check api status
Checks if the TIDAL Developer service is currently operational.
Get album tracks
Gets all tracks belonging to a specific album using its ID.
Get artist albums
Retrieves all albums associated with a given artist ID.
Verifies if the entire TIDAL Developer service is currently running.
Find albums by name or artist, retrieving basic metadata like track count and duration.
Locates artists within the TIDAL catalog using their known names.
Retrieves a list of all albums associated with a specific artist ID.
Fetches every track, along with its metadata, for an album identified by its unique ID.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
TIDAL Developer API MCP Server: 5 Tools for Metadata Retrieval
These five tools allow your agent to search, locate, and retrieve specific music metadata—from artist IDs to individual track lists.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using TIDAL Developer API on Vinkius019d848dcheck api status
Checks if the TIDAL Developer service is currently operational.
019d848dget album tracks
Gets all tracks belonging to a specific album using its ID.
019d848dget artist albums
Retrieves all albums associated with a given artist ID.
019d848dsearch tidal albums
Searches for albums on TIDAL using either the album name or the artist name.
019d848dsearch tidal artists
Searches and locates artists within the TIDAL catalog.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with TIDAL Developer API, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by TIDAL. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 5 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Finding music metadata shouldn't require multiple tabs and copy-pasting IDs.
Today, if you need to audit an artist’s history, you manually search for the artist name. Then you open a new tab for each album to find its ID. You then have to piece together track counts and durations from various web pages—it's slow, error-prone, and tedious.
With this MCP server, your agent handles it all in one go. Tell it: 'Give me the full discography.' It runs `search_tidal_artists` first, then loops through results using `get_artist_albums`. You get a clean JSON object of every album title and ID—no more clicking.
TIDAL Developer API MCP Server: Get structured music data in plain conversation.
Before, getting the tracklist for an entire project meant knowing the specific album ID and then navigating to a dedicated page. If you missed one step or used the wrong identifier, the process broke.
Now, your agent knows the workflow. You simply ask: 'Show me all tracks for album X.' It automatically runs `get_album_tracks`, pulling every title, duration, and ID into a single, usable block of data. That's the difference.
What you can do with this MCP connector
Your AI client uses the TIDAL Developer API to pull structured music data right from TIDAL's catalog. You don't gotta log into a separate streaming app; your agent handles all the heavy lifting, letting you audit discographies and get precise metadata points. It’s built for deep research—the kind of stuff an industry analyst needs when they can't just click around in an interface.
When you need to know if the service is even up, start with check_api_status. That single call confirms whether the entire TIDAL Developer service is running smoothly. If that tool doesn't pass, none of the other calls matter, so it’s always smart to check first.
Need to find an album? You can use search_tidal_albums to hunt for records by either the album name or the artist's name. This search returns basic metadata like how many tracks are on the record and what the total duration is, helping you narrow down your target quickly before diving deeper into specific IDs.
If you start with an artist's name instead of an album title, search_tidal_artists locates that artist within the TIDAL catalog. This gives you the essential artist ID needed for everything else. Once you have that ID, you can immediately call get_artist_albums. That tool doesn't just give you a few albums; it retrieves every single album associated with that specific artist ID, letting you map out their entire recorded discography.
If you know the exact name of an album but don't have its ID yet, you can use search_tidal_albums again. This finds the album and gives you the necessary metadata to proceed. If you already have that unique album ID, calling get_album_tracks fetches every single track belonging to it. You get a complete list of tracks, each with detailed associated metadata.
These tools let your agent go beyond simple search results. They provide granular data points: the specific identifiers for any given piece of music, precise duration markers, and comprehensive lists that map out an artist’s full output. For instance, you can combine search_tidal_artists to find an ID, use that ID with get_artist_albums to get a list of five albums, then pick one album's ID and pass it into get_album_tracks to pull every single tracklist for analysis.
You don't need any manual steps or guesswork; your agent runs the workflow based on what you prompt it with.
019d848e-0b1b-7354-b0f5-e70d3ed4d352 
How TIDAL Developer API MCP Works
- 1 Subscribe to the TIDAL Developer API server and input your key.
- 2 Your AI client runs a natural language query (e.g., 'Find all tracks for album XYZ').
- 3 The agent executes the necessary tool call, pulls the structured metadata, and gives you a direct answer.
The bottom line is: your agent handles complex music searches by calling specific functions on the TIDAL backend, so you don't have to.
Who Is TIDAL Developer API MCP For?
Music journalists who need to fact-check release dates. Curators and DJs needing instant track duration verification. App developers building music data tools that require deep catalog auditing.
Audits entire artist catalogs, pulling official metadata straight into reports to map out a musician's distribution scale.
Verifies track durations and checks album availability across an artist's discography without manual searching.
Performs rapid, automated audits of music data to identify stylistic markers or required content for a new application feature.
What Changes When You Connect
- Deep Metadata Access: Forget guessing. You get high-resolution identifiers and exact duration markers for any track via
get_album_tracksor the main API calls. This is essential for classification tasks. - Rapid Discovery: Need to find a specific album? Use
search_tidal_albums. It lets your agent locate albums based on name or artist, saving you manual browsing time in music apps. - Full Discography View: Don't just look at one project. The
get_artist_albumstool gives you the complete list of every album an artist has released by ID. - Process Control: Always confirm the API is up first. Use
check_api_statusto ensure your entire music research workflow starts and ends reliably. - Structured Data Flow: The agent processes results from multiple tools—say, finding an artist (
search_tidal_artists) then getting their albums (get_artist_albums)—and presents it all in a clean format.
Real-World Use Cases
Verifying Album Details for a Feature
A music journalist needs to confirm the track count and release date of an album. They ask their agent, which first uses search_tidal_albums (by name) and then confirms the details using the core metadata tools. The problem is solved instantly with structured data.
Mapping an Artist's Career Timeline
A curator wants to see every album released by Daft Punk. They instruct their agent to use search_tidal_artists first, then feed the resulting ID into get_artist_albums. This instantly provides a complete view of their discography for planning.
Debugging Tracklist Issues
A developer needs to know every track in an album with a specific ID. Instead of digging through the web, they prompt the agent, which executes get_album_tracks. They get 10 entries, each with its duration and unique identifier—no guesswork.
Cross-Checking Metadata Reliability
Before running a major analysis, an ops lead asks for system health. The agent runs check_api_status first. If the status is green, they know their entire cross-functional creative team workflow can proceed.
The Tradeoffs
Over-relying on general web search
Manually searching Google for 'Beyoncé albums' and then clicking through links to piece together a discography timeline.
→
Use the agent. Start by running search_tidal_artists with 'Beyoncé'. Then, feed that resulting ID directly into get_artist_albums to get the full list of titles needed.
Assuming all data is available
Writing a script that fails because it assumes an album exists when you only know the artist name.
→
Always validate first. Use check_api_status to confirm service uptime, and then use search_tidal_albums with fallback logic instead of assuming the ID is correct.
Mixing up search types
Trying to get tracks for an album using only a general artist name.
→
You need two steps. First, use search_tidal_albums to find the album and get its specific ID. Second, pass that unique ID into get_album_tracks.
When It Fits, When It Doesn't
Use this server if your primary goal is structured, deep data auditing of music catalogs (metadata, tracks, artists). You need programmatic access to discographies and reliable identifiers. Don't use it if you just want to listen to music or check general streaming availability; that’s what a standard music app does.
If you only know the album title but not the artist, start with search_tidal_albums. If you already have the Artist ID, skip the search and go straight to get_artist_albums for efficiency. Only use get_album_tracks when you have a confirmed Album ID—that's its specific job.
Common Questions About TIDAL Developer API MCP
How do I find an artist's full list of albums using search_tidal_artists? +
You first use search_tidal_artists to get the correct Artist ID. Then, take that ID and pass it into the get_artist_albums tool. This gets you every album title they have recorded.
Should I use search_tidal_albums or get_album_tracks? +
Use search_tidal_albums if you only know the name and need to find the ID first. Use get_album_tracks when you already have a specific Album ID and want the full list of songs.
What is the best way to check service reliability with TIDAL Developer API? +
Run the check_api_status tool. This instantly tells your agent if the entire music research workflow can proceed or if there's an issue with the connection.
Can I search for albums by artist name using TIDAL Developer API? +
Yes, use search_tidal_albums. This tool allows you to input either the album title or the artist name into a single query and find matching records.
What is required before I can use `search_tidal_albums`? +
You must provide a valid TIDAL Developer API key in your agent's configuration. Once connected, your AI client uses that key to make authenticated requests, allowing it to search for albums and retrieve metadata.
If I only have an album name, how do I get the track list using `get_album_tracks`? +
You cannot use get_album_tracks directly with a name. First, you must run search_tidal_albums to find the correct Album ID. Then, pass that unique ID into the get_album_tracks tool.
How do I handle rate limits when using `get_artist_albums`? +
If you hit a usage limit, the API will return an error code indicating rate throttling. Your agent needs to implement exponential backoff—meaning it should wait progressively longer periods before retrying the call.
Can `get_album_tracks` provide only track durations and identifiers? +
The tool returns a full data object for every track. You can process this returned structure to filter out any fields you don't need, giving your agent just the duration markers and unique IDs.
How do I find my TIDAL API Key? +
Register at the TIDAL Developer portal, create an application, and you will receive your API Key. Copy and paste it below.
Can the agent show track durations? +
Yes. Every track record retrieved by your agent includes metadata on the duration in seconds, which is automatically converted to minutes and seconds.
Does it support high-resolution audio info? +
Yes. The TIDAL API provides metadata indicating available audio qualities (e.g., Lossless, High) for albums and tracks.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.