MyMusik MCP
Related Servers
Alternatives to MyMusik MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables Claude and other MCP clients to search tracks, albums, artists, and playlists; control playback and the queue; and create or edit playlists through natural language.5MIT
- AlicenseBqualityCmaintenanceLets Claude or any MCP client drive the macOS Music app locally to control playback, search the library, build and edit playlists, set favorites, and pull listening statistics like top tracks, artists, albums, and genres.17MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to a local music library for full-text search and filtering of tracks, albums, artists, genres, composers, and lyrics, plus listening analytics and metadata hygiene audits. Also lets users generate and populate playlists and control playback (play, pause, seek, volume) in a running player instance.MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to search and browse music catalogs and libraries, manage playlists and favorites, control playback, and view or modify the Up Next queue across macOS, Windows, and Linux.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to search and manage playlists, library, catalog, discovery, playback, and the Up Next queue across macOS, Windows, and Linux.-
- 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.-
TDQS
Scored across 1 tool
There is only one tool in the set, so there is no ambiguity about which tool to select. Its purpose—controlling the current playback queue—is clearly stated and distinct from search/API tools mentioned elsewhere.
The single tool uses a clear snake_case server-prefixed pattern, mymusik_playback. With only one tool, there is no inconsistency in convention.
A single tool is too thin for a server named MyMusik MCP, which implies broader music control. The one tool bundles several playback actions but leaves the overall server surface underspecified.
The tool covers resume, pause, next, and previous, but lacks play-by-name, queue inspection, volume, seek, shuffle, and other common playback operations. The description explicitly points users to other tools for playing a particular song, album, or playlist, which is a notable gap.