Skip to main content
Glama
Robert-ArcturionTech

spotify-mcp

by Robert-ArcturionTech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to spotify-mcp

No user-submitted related servers found.

    Related Servers

    • netease-music-mcp

      yxrytcuucuc
      A
      license
      A
      quality
      B
      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

    • YouTube MCP Server

      CreatorGeetansh
      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

    • soundcloud-mcp

      auxa-m45
      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

    • spotify-mcp

      seenws
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to build and edit Spotify playlists from natural language descriptions.
      7
      81 npm
      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

    C2.7/5.0

    Scored across 36 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource or action, and the playback/library/playlist clusters are cleanly separated. The main overlap is playlist_rename versus playlist_set_details (both can change a playlist's name), and resolve versus search have related but distinguishable purposes.

    Naming Consistency3/5

    Naming mixes conventions: single verbs (play, pause, skip), noun-first (saved_tracks, now_playing, top_tracks), verb_noun (save_albums, follow_artists), and noun_verb for the playlist_* family. The playlist_ prefix is internally consistent and everything stays readable, but there is no single predictable pattern across the server.

    Tool Count3/5

    36 tools is on the heavy side, but the domain (playback control, library, discovery, and full playlist CRUD) genuinely warrants many operations. It sits at the borderline where a few tools (e.g. separate rename and set_details) could be consolidated.

    Completeness4/5

    Coverage is broad and coherent: playback, library management, search/discovery, and playlist lifecycle all have create/read/update/delete paths with sensible destructive guards. Minor gaps remain, e.g. shuffle/repeat mode toggles and dedicated album/artist detail retrieval.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources