Skip to main content
Glama
sickn33

TIDAL MCP

by sickn33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to TIDAL MCP

No user-submitted related servers found.

    Related Servers

    • youtube-music-mcp

      ElisonSz
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables searching YouTube Music and managing playlists through read and confirmation-gated write tools over STDIO. Supports identity checks, song search, playlist listing/retrieval, and previewed playlist creation, track addition, and exact track removal.
      MIT

    • mcp-auth-proxy

      manio143
      F
      license
      Not graded
      quality
      D
      maintenance
      Bridges stdio-based LLM harnesses to OAuth-protected remote MCP servers via Streamable HTTP, handling PKCE browser login and token refresh automatically.
      9 npm
      -

    • YT Music Manager

      Robin-Kurian
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding tools and MCP hosts to search YouTube Music and add or remove tracks on your own playlists through natural-language prompts, authenticated with your Google login. It runs locally over stdio, so credentials and OAuth tokens stay on your machine.
      -

    • yt-mcp

      stevenmichiels
      A
      license
      A
      quality
      A
      maintenance
      Enables local stdio access to YouTube Music song search, song-radio recommendations, and creation of private playlists in a connected Google account.
      6
      MIT

    • hinge-mcp

      Kuberwastaken
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables assistants to sign in to and interact with a user's own Hinge account through MCP tools, resources, and prompts, including session lifecycle and account reads. Runs locally over stdio or Streamable HTTP with authentication options.
      7
      MIT
    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

    C2.9/5.0

    Scored across 112 tools

    Disambiguation3/5

    Many tools have closely related names (e.g., tidal_get_playlist_tracks vs tidal_get_playlist_items, tidal_list_playlists vs tidal_list_public_playlists vs tidal_list_playlists_and_favorites, tidal_get_track_playback_info vs tidal_get_track_audio_resolution). Descriptions clarify the differences, but the sheer number of similar read and preview variants creates moderate ambiguity for an agent.

    Naming Consistency4/5

    All tools use the tidal_ prefix and snake_case with a consistent action_verb pattern (get_, list_, browse_, preview_, commit_). Minor inconsistencies like singular/plural (add_track vs add_tracks) and version suffixes (_v2) prevent a perfect score.

    Tool Count1/5

    112 tools far exceeds a reasonable scope for an agent-facing toolset. Many read endpoints and the preview/commit pattern could be consolidated (e.g., generic page readers, image size parameters), making this an extreme mismatch.

    Completeness4/5

    The surface covers catalog browsing, playlist and folder CRUD, favorites management, playback URLs, lyrics, radio, and browse pages comprehensively. Gaps like playback control, track credits, or user profile editing are minor relative to the extensive coverage.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources