Skip to main content
Glama
yuhuacheng

TIDAL MCP: My Custom Picks

by yuhuacheng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to TIDAL MCP: My Custom Picks

No user-submitted related servers found.

    Related Servers

    • TIDAL MCP

      ibeal
      A
      license
      A
      quality
      A
      maintenance
      A community-maintained MCP server for TIDAL that enables personalized music recommendations, full playlist management, and advanced search across tracks, albums, artists, and playlists via natural language.
      19
      6
      MIT

    • commendation

      umsachde
      A
      license
      A
      quality
      B
      maintenance
      MCP server that recommends new songs from YouTube Music, ensuring no song is already liked or in any playlist, using multiple independent signals for explainable rankings.
      10
      MIT

    • AUX

      brian-mwirigi
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that turns your AI into a Spotify DJ, enabling mood-based playback, auto-DJ, party rooms, and playlist roasting.
      1
      MIT

    • MCP PLAYLIST SERVER

      alee2602
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides intelligent playlist curation tools using Spotify track data and audio feature analysis. It enables AI assistants to create mood-based playlists, find similar songs, analyze audio characteristics, and curate personalized music collections.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a distinct purpose with no overlap: create/delete playlists, get favorites, get playlist tracks, get user playlists, recommend tracks, and login. The descriptions clearly differentiate them, and an agent can easily select the correct tool for any TIDAL-related request without confusion.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'tidal' prefix (e.g., create_tidal_playlist, get_favorite_tracks, recommend_tracks). The naming is uniform and predictable, making it easy for agents to understand and use the toolset.

    Tool Count5/5

    With 7 tools, this server is well-scoped for managing TIDAL playlists and recommendations. It covers essential operations (CRUD for playlists, fetching tracks, login) without being too sparse or bloated, making each tool valuable and necessary for the domain.

    Completeness4/5

    The toolset provides strong coverage for playlist management (create, delete, list, view tracks) and recommendations, with a login tool for authentication. A minor gap is the lack of an update_playlist tool for modifying existing playlists, but agents can work around this by deleting and recreating. Overall, it supports core TIDAL workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources