Skip to main content
Glama
Whyomi1122

netease-music-mcp

by Whyomi1122
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to netease-music-mcp

No user-submitted related servers found.

    Related Servers

    • netease-mcp

      xiaocaoooo
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI assistants to search and retrieve music data (songs, lyrics, playlists, albums, artists) from Netease Cloud Music.
      MIT

    • CloudmusicMCP

      LoranaAurelia
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching NetEase Cloud Music and safely managing playlists through a local stdio MCP server with automatic backend lifecycle management.
      MIT

    • netease-music-mcp

      luuu-h
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling local music playback via NetEase Cloud Music, enabling search, play, pause, skip, and lyrics display through a local web player.
      13
      77
      MIT

    • music-mcp

      xiaonanbo1998
      F
      license
      B
      quality
      B
      maintenance
      A 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
      -

    • netease-music-mcp

      GBAIOT
      A
      license
      Not graded
      quality
      C
      maintenance
      非官方MCP服务，允许通过统一的工具接口操作网易云音乐，包括搜索歌曲、创建与管理歌单、查看听歌记录、收藏歌曲及获取每日推荐。
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools map to clearly distinct resource-action pairs: playlist operations, song metadata/search, lyrics, and macOS client controls are well separated. The main overlap is netease_next_track versus netease_control, which both cover the next-track action, and netease_status versus netease_playlist_auth_status are somewhat similar in name but distinct in purpose.

    Naming Consistency4/5

    All tools use a consistent snake_case format with the netease_ prefix, which is readable and predictable. There are minor deviations: some names are noun-like (song_detail, lyrics, status) while others are verb-based (search, launch, playlist_create), but the overall pattern is still recognizable.

    Tool Count4/5

    17 tools is slightly above the ideal range but reasonable for a server that covers playlist management, song discovery, lyrics, and macOS client control. Most tools are narrow and functional, though a few could potentially be consolidated without much loss.

    Completeness3/5

    Playlist management covers create, list, add, remove, and read operations, but lacks playlist rename or delete. Playback control is present, but there is no way to retrieve the current playing track or directly play a specific song, which are notable gaps for a music-focused server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources