Skip to main content
Glama
RomitDeokar

mcp-spotify

by RomitDeokar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-spotify

No user-submitted related servers found.

    Related Servers

    • Spotify MCP Server

      nlevy
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that provides Spotify integration, allowing AI assistants and applications to interact with Spotify's music streaming service.
      12
      1
      MIT

    • spotify-mcp-server

      qchuchu
      A
      license
      Not graded
      quality
      D
      maintenance
      An unofficial MCP server that provides access to Spotify's Web API through the Model Context Protocol, enabling AI assistants to search music, manage playlists, and control playback.
      6 npm
      9
      ISC

    • spotify-mcp

      markandeyay
      A
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server for Spotify with brokered OAuth and server-side intelligence, enabling search, playlist management, playback control, library analysis, and listening trends via natural language.
      38 npm
      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

    B3.4/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, but get_playlist_tracks and get_playlist_items appear to overlap significantly. get_playlist also overlaps with those, creating some ambiguity between playlist detail-fetching operations.

    Naming Consistency5/5

    Consistent verb_noun pattern throughout: get_*, add_*, remove_*, modify_*, search. The one bare 'search' is a minor deviation but universally understood in this domain.

    Tool Count4/5

    24 tools is at the high end but justified by Spotify's broad catalog surface (tracks, albums, artists, playlists, audiobooks). A few tools like get_multiple_* variants could potentially be consolidated.

    Completeness4/5

    Strong read coverage across catalog entities and playlist lifecycle (create via modify? no create_playlist is missing). Playlist creation is a notable gap, as is user profile/playback control, but core browsing and playlist mutation workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources