Yandex Music MCP
Related Servers
Alternatives to Yandex Music MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a local stdio MCP server for controlling YouTube Music through the CLI, enabling playback, search, queue management, and library access via MCP-compatible clients.MIT
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that turns Yandex Music into tools an AI agent can call directly — search, queue, play, build playlists — with no browser involved.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients like Claude, Cursor, Cline, and Windsurf to search and browse the Apple Music catalog and library, manage playlists and folders, rate and favorite tracks, control playback, and view or edit the Up Next queue. It works on macOS, Windows, and Linux through four interchangeable engines (native Music.app, Apple Music API, Safari, and Chrome), requiring only a Mac or an Apple Music subscription.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients like Claude, Cursor, Cline, and Windsurf to search and browse the Apple Music catalog and your library, manage playlists and folders, and control playback, volume, and the Up Next queue. It works on macOS, Windows, and Linux through four selectable engines — native Music.app, the Apple Music API, Safari MusicKit, or a Chrome web player — requiring only a Mac or an Apple Music subscription.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients like Claude, Cursor, Cline, and Windsurf to search and browse the Apple Music catalog and library, manage playlists and favorites, control playback, and drive the Up Next queue on macOS, Windows, and Linux. It works with just a Mac or an Apple Music subscription, automatically choosing among native Music.app, Safari, Chrome, and Apple Music API engines.-
TDQS
Scored across 19 tools
Most tools target a clearly distinct resource+action pair: liked tracks, charts, playlists, albums, artists, search, history, wave, and export are all separable. The only real friction is between get_playlist_tracks, get_playlist_by_url, and get_album_tracks, where the same content can be reached via id, owner_uid, or URL — descriptions mostly resolve this but an agent may still hesitate on which entry point to use.
Strong consistent snake_case verb_noun pattern across nearly all tools (get_liked_tracks, create_playlist, add_tracks_to_playlist, export_tracks_to_file, list_my_playlists). Two deviations break it: bare 'search' and the noun-phrase 'account_info' (would be get_account_info / search_catalog), plus a couple of prepositional variants.
At 19 tools the set is on the heavier side but each tool maps to a concrete capability of the music service, with no filler or near-duplicates. Nothing feels padded, though it brushes the upper bound of easy scannability for an agent.
Playlist lifecycle is largely covered (create, list, get tracks, add/remove tracks, delete, export) alongside liked tracks, search, charts, history, and radio-style discovery. Gaps are minor: no playlist rename/edit (title, description, cover), no direct get_track_by_id for track-level metadata, and no liked-albums/artists management.