netease-music-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETEASE_CSRF | No | The CSRF token cookie value (alternative to full cookie). | |
| NETEASE_COOKIE | No | The complete cookie string for NetEase authentication (alternative to NETEASE_MUSIC_U and NETEASE_CSRF). | |
| NETEASE_MUSIC_U | No | The MUSIC_U cookie value (alternative to full cookie). | |
| NETEASE_USER_ID | No | Your NetEase user ID, required for accessing personal music library. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| music_searchB | Search songs, artists, albums, or playlists with compact paginated results. |
| get_recommendationsA | Read a page of NetEase's read-only recommended playlists. |
| get_similar_songsA | Read a page of songs similar to one NetEase song. |
| get_new_songsA | Read a page of recommended new songs by region. |
| get_rankingsA | Read a page of NetEase ranking boards with compact top tracks. |
| get_songsA | Fetch metadata for multiple songs in one call while preserving input order. |
| get_albumA | Fetch album metadata and optionally one page of tracks. |
| get_artistB | Fetch artist metadata and optionally a bounded list of top songs. |
| get_playlistA | Fetch playlist metadata and optionally one bounded page of tracks. |
| get_lyricsB | Fetch a bounded lyric page with optional aligned translation and romanization. |
| get_user_libraryA | Read one authenticated, paginated section of a user's music library. |
| get_playlist_statisticsB | Compute deterministic duration, artist, album, year, and availability statistics. |
| create_playlistA | Create a NetEase playlist after explicit confirmation. |
| update_playlist_tracksB | Add or remove songs from a NetEase playlist after confirmation. |
| set_song_likeA | Like or unlike one NetEase song after explicit confirmation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.