Tidal Mcp
Let your agent search TIDAL, manage playlists, and fetch recommendations for music-aware apps or personal workflows.
Overview
TIDAL MCP is a MCP server for the Build phase that lets agents search TIDAL, manage playlists, and read personalized recommendations.
What is this MCP server?
- Search TIDAL tracks from MCP-connected agents
- Create and manage playlists programmatically
- Personalized recommendation access via MCP tools
- OCI package ghcr.io/ibeal/tidal-mcp:latest with stdio transport
- Optional TIDAL_MCP_PORT for the backing Flask API (default 5050)
- Registry version 0.4.0
- Default TIDAL API Flask port 5050 via TIDAL_MCP_PORT
- OCI identifier ghcr.io/ibeal/tidal-mcp:latest
Community signal: 4 GitHub stars.
What problem does it solve?
Agents cannot touch your TIDAL library or discovery flow without a dedicated API bridge and OAuth-aware tooling.
Who is it for?
Builders shipping music-adjacent agents, bots, or side projects that need TIDAL search and playlist control from the IDE.
Skip if: Teams with no TIDAL subscription or products that do not need streaming-catalog integration.
What do I get? / Deliverables
Your agent can query tracks, adjust playlists, and pull recommendations through stdio MCP tools backed by the tidal-mcp container.
- Agent tools for TIDAL track search
- Programmatic playlist create and update flows
- Recommendation queries exposed through MCP
Recommended MCP Servers
Journey fit
How it compares
TIDAL streaming integration MCP, not a DAW plugin or generic Spotify skill.
Common Questions / FAQ
Who is TIDAL MCP for?
Developers using AI agents who want programmatic TIDAL search, playlists, and recommendations in side projects or music-aware automations.
When should I use TIDAL MCP?
Use it while building integrations that must read or modify TIDAL content from Claude Code, Cursor, or another MCP client.
How do I add TIDAL MCP to my agent?
Run the OCI image ghcr.io/ibeal/tidal-mcp:latest with stdio transport, set TIDAL_MCP_PORT if needed, complete TIDAL auth per the GitHub repo, and register the server in your MCP config.