netease-music-mcp
Related Servers
Alternatives to netease-music-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to search songs, retrieve details and lyrics, and manage personal playlists on NetEase Cloud Music, with optional local player control on macOS, all through a privacy-first, self-hosted service.17MIT
- AlicenseAqualityBmaintenanceA read-only MCP server for NetEase Cloud Music data, enabling querying of songs, artists, albums, playlists, lyrics, and user library through tools like search and get details.153MIT
- AlicenseNot gradedqualityCmaintenance非官方MCP服务,允许通过统一的工具接口操作网易云音乐,包括搜索歌曲、创建与管理歌单、查看听歌记录、收藏歌曲及获取每日推荐。1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to search and read YouTube data and safely manage playlists, including creating private playlists from ranked song matches with preview-before-commit playlist mutations.1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI assistants to search and retrieve music data (songs, lyrics, playlists, albums, artists) from Netease Cloud Music.MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to search SoundCloud and retrieve tracks, playlists, and users, as well as perform authenticated actions such as likes, reposts, follows, comments, playlist editing, and uploads with multi-account OAuth support.36MIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource or action: search vs discovery feeds vs entity fetch vs lyrics vs library vs stats vs mutations. Overlaps like get_playlist and get_playlist_statistics are clearly separated by description and output intent.
Most tools follow a verb_noun pattern with get_/create_/update_/set_ prefixes, which is consistent and readable. music_search deviates as noun_verb; a name like search_music would align better.
15 tools is well-scoped for a music service, covering discovery, metadata, lyrics, library access, and playlist/like mutations. Each tool has a recognizable purpose without excessive surface area.
Core workflows are covered: search, discovery, entity metadata, lyrics, user library, stats, playlist creation/update, and like/unlike. However, playlist lifecycle lacks delete/rename operations, and user-library modifications beyond likes are not exposed, leaving minor gaps.