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

    • AKIMCP

      rina19326
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a governed suite of 38 OAuth-gated MCP tools that let web-based AI chats and other clients read and edit files, run whitelisted shell commands, search, use Git, SQLite, browser automation, DevTools, background tasks, localhost services, clipboard, notifications, and ports on a user's own machine. It runs locally with folder scoping and a strict command whitelist, so remote clients gain a large operating surface without unrestricted shell access.
      -

    • 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

    • Yandex Music MCP

      kenzolika
      A
      license
      B
      quality
      A
      maintenance
      Connects Claude and other MCP clients to a user's Yandex Music account so they can search the catalog, read liked tracks, listening history, My Wave and playlists, create and edit playlists, like or unlike tracks, and export the library to .txt or .csv. It runs locally over stdio with the token kept on the user's machine, and it does not download audio.
      19
      53 PyPI
      1
      MIT

    • aki-mcp-sv

      henrymartin33
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes 38 OAuth-gated tools over one MCP endpoint so web-based AI clients like Claude, ChatGPT, and Grok can read and edit local files, run whitelisted shell commands, search content, use Git, SQLite, browser automation, DevTools, clipboard, notifications, ports, and background jobs on your own machine. A strict command whitelist and folder restrictions keep the local operating surface governable and safe by default.
      -

    • AKIMCP

      Sasaki2454
      F
      license
      Not graded
      quality
      A
      maintenance
      Exposes an OAuth-gated MCP endpoint with a governed suite of 38 tools that let web-based AI chat clients work directly on your local machine — reading and editing files, running whitelisted shell commands, searching, using Git and SQLite, automating browsers, driving DevTools, managing background tasks and ports, and reaching localhost services, clipboard, and notifications. A strict command whitelist and folder-scoped access keep that remote operating surface safe by default.
      -
    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 117 tools

    Disambiguation3/5

    Several tool families overlap heavily (e.g., playlist tracks vs. playlist items, album tracks vs. album items, legacy vs. v2 mixes, playback info vs. audio resolution), but the detailed descriptions usually clarify the intended distinction. An agent can generally disambiguate with careful reading, though the set forces extra cognitive work.

    Naming Consistency5/5

    All tools use the `tidal_` prefix and snake_case consistently, with verbs like get, list, browse, preview, and commit used systematically. The lone backward-compatibility alias (`tidal_commit_create_playlist`) is clearly labeled and does not meaningfully break the pattern.

    Tool Count1/5

    With 117 tools, this is far beyond the 3-15 range and exceeds even the 25+ threshold for 'too many' by a wide margin. Even accounting for TIDAL's broad API, the surface is overwhelming and likely to hinder an agent's selection process.

    Completeness4/5

    The set covers discovery, catalog metadata, favorites, playlists, folders, radio, lyrics, playback URLs, and a preview/commit mutation pattern. A few niche operations (e.g., artist-following, mood-item retrieval, or page-level CRUD) appear absent, but most core workflows are supported without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources