Skip to main content
Glama
Code-MonkeyZhang

Cloud Music MCP Server

by Code-MonkeyZhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Cloud Music MCP Server

No user-submitted related servers found.

    Related Servers

    • CloudMusic Desktop MCP

      Seraph310
      A
      license
      Not graded
      quality
      C
      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

    • netease-desktop-mcp

      WalterT812
      A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control the Windows NetEase Cloud Music desktop app via local stdio MCP, including reading current song and liked state, searching and playing tracks, playback control, track skipping, and setting the current song's liked status.
      10
      MIT

    • netease-music-mcp

      GBAIOT
      A
      license
      Not graded
      quality
      C
      maintenance
      非官方MCP服务，允许通过统一的工具接口操作网易云音乐，包括搜索歌曲、创建与管理歌单、查看听歌记录、收藏歌曲及获取每日推荐。
      1
      MIT

    • qq-music-mcp

      wangkezun
      A
      license
      A
      quality
      D
      maintenance
      Integrates QQ Music API with MCP, enabling LLMs to search music, retrieve song details, lyrics, and playback URLs.
      10
      4
      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.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose, from login and search to playlist management and playback. There is no ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent 'cloud_music_' prefix with snake_case verb_noun pattern (e.g., add_to_playlist, create_playlist, get_daily_recommend), making naming predictable.

    Tool Count4/5

    12 tools are appropriate for a cloud music server, covering search, details, playlist management, login, and playback. Slightly over the ideal range but each tool earns its place.

    Completeness3/5

    Core workflows like search, get details, create playlist, add tracks, and play are covered. However, notable gaps exist: no tools to remove tracks, delete playlists, or manage likes, limiting full lifecycle coverage.

    Maintenance

    ActivityStale
    ResponsivenessSlow

    Resources