Skip to main content
Glama
WalterT812

netease-desktop-mcp

by WalterT812
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to netease-desktop-mcp

No user-submitted related servers found.

    Related Servers

    • CloudMusic Desktop MCP

      Seraph310
      A
      license
      Not graded
      quality
      D
      maintenance
      Controls the official NetEase Cloud Music desktop client on Windows, enabling AI to search, play, manage queues, and adjust playback settings via a local control channel.
      1
      MIT

    • Orpheus

      SUPERtongmeng
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control a local NetEase Cloud Music client in natural language — searching songs and playlists, playing or queuing tracks, replacing the queue with a playlist, and pausing, skipping, or adjusting volume — via a BetterNCM plugin and localhost bridge with token authentication.
      9 npm
      MIT

    • CloudmusicMCP

      LoranaAurelia
      A
      license
      Not graded
      quality
      D
      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

      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

    A4.3/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct action: observing status, searching, playing a specific result, toggling playback, skipping, liking, and playlist creation/listing/deletion. The two-step playlist delete preview is clearly separated from the actual delete, and playback controls are differentiated by target and behavior.

    Naming Consistency4/5

    Tool names follow a consistent netease_ prefix and mostly use verb_noun (netease_get_status, netease_create_playlist, netease_delete_playlist). Minor deviations like netease_search (verb only) and netease_set_liked (verb + adjective rather than a noun) keep the overall pattern readable but not fully uniform.

    Tool Count5/5

    Ten tools is a well-scoped size for controlling a desktop music app and managing playlists. Each tool covers a distinct capability without redundant helpers or excessive granularity.

    Completeness3/5

    Core playback/search/like flows are well covered, and playlists create/list/delete exists as a lifecycle. However, there is no tool to add or remove tracks from a playlist or inspect playlist contents, so a created playlist remains an empty dead end for many real workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources