netease-music-mcp
Related Servers
Alternatives to netease-music-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI assistants to search and retrieve music data (songs, lyrics, playlists, albums, artists) from Netease Cloud Music.MIT
- AlicenseAqualityDmaintenanceMCP server for controlling local music playback via NetEase Cloud Music, enabling search, play, pause, skip, and lyrics display through a local web player.1380MIT
- FlicenseBqualityBmaintenanceA local music retrieval MCP server that lets users search, download, and organize songs via natural language, with lyrics matching from NetEase Cloud Music and LRCLIB, plus local library indexing through SQLite.5-
- AlicenseCqualityAmaintenanceMulti-source music search and playback MCP server supporting QQ Music, NetEase Cloud, and local files with playlist management.32MIT
- 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
- AlicenseNot gradedqualityCmaintenance非官方MCP服务,允许通过统一的工具接口操作网易云音乐,包括搜索歌曲、创建与管理歌单、查看听歌记录、收藏歌曲及获取每日推荐。1MIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource or action: search, various recommendation feeds, metadata lookups by type, lyrics, library, statistics, and write operations. Potential overlaps like 'get_recommendations' vs 'get_new_songs' are clearly separated by content type and description, leaving no ambiguity.
Most tools follow a verb_noun snake_case pattern (get_*, create_*, update_*, set_*), which is highly consistent. The sole exception is 'music_search', which reverses the order (noun_verb) instead of 'search_music', but this is a minor deviation in an otherwise predictable set.
15 tools is well-scoped for a music service, covering search, discovery, metadata retrieval, user library access, statistics, and playlist management. Each tool has a clear and justified place, with no redundant or filler tools.
The tool surface covers the core lifecycle: browsing, searching, fetching details, managing playlists, and liking songs. Minor gaps include no delete playlist operation, no user profile endpoint, and limited artist discography, but these are workaroundable and do not severely hinder typical music workflows.