Skip to main content
Glama
Sign In
xinyu68

netease-music-mcp

by xinyu68
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to netease-music-mcp

No user-submitted related servers found.

    Related Servers

    • NetEase Music Local MCP

      S4kuzy0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local QR-code login to NetEase Cloud Music and read-only access to complete liked-song pagination, playlists, search, song details, daily recommendations, and listening history with whole-library recommendation de-duplication.
      MIT

    • netease-music-mcp

      yxrytcuucuc
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to query NetEase Cloud Music data such as songs, artists, albums, playlists, lyrics, and a logged-in user's library in compact, paginated, structured form, along with guarded playlist and like write operations.
      15
      MIT

    • Spotify MCP

      abenke
      A
      license
      A
      quality
      D
      maintenance
      Enables searching and managing Spotify playlists, tracks, and user information through the Spotify Web API.
      10
      MIT

    • SpotifyMCP

      NovaLux12
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to control Spotify playback, search the full catalog including podcasts and audiobooks, manage libraries and playlists, and understand listening taste.
      131
      347 npm
      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

    B3.3/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct playback, library, account, or search purposes. Some overlap remains between generic playback and source-specific play tools, and between netease_song_detail and netease_lyrics, but descriptions generally resolve these boundaries.

    Naming Consistency5/5

    All tools consistently use the netease_ prefix followed by snake_case names. Although some names are verb-led and others noun-led, the overall convention is predictable and easy to scan.

    Tool Count3/5

    At 25 tools, the surface is at the heavy end for a music playback server. Several source-specific play tools could likely be consolidated, though each control still has a plausible role.

    Completeness4/5

    Core playback, queue navigation, search, lyrics, account status, and library browsing are well covered. Minor gaps exist around queue modification and playlist management, but the main agent workflows are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources