Skip to main content
Glama
yxrytcuucuc

netease-music-mcp

by yxrytcuucuc

Related Servers

Alternatives to netease-music-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      17
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      15
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      非官方MCP服务,允许通过统一的工具接口操作网易云音乐,包括搜索歌曲、创建与管理歌单、查看听歌记录、收藏歌曲及获取每日推荐。
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      Apache 2.0
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      36
      MIT

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues