Skip to main content
Glama
thebigredgeek

spotify-mcp-server

by thebigredgeek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to spotify-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCP Spotify Server

      fborello
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Spotify through LLMs using OAuth2 authentication. Supports music search, playback control, playlist management, and device management through natural language commands.
      14
      2
      MIT

    • Spotify MCP Server

      EvansLR
      F
      license
      A
      quality
      D
      maintenance
      Enables control of Spotify playback through OAuth authentication, including play/pause, track navigation, volume control, device management, and searching/playing songs by artist or track name.
      11
      1
      -

    • Spotify MCP Server

      nicklaustrup
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Spotify through natural language for music discovery, playback control, library management, and playlist creation. Supports searching for music, controlling playback, managing saved tracks, and getting personalized recommendations based on mood and preferences.
      53 npm
      5
      MIT

    • Spotify MCP Server

      gentiku
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables control of Spotify playback, music search, and playlist management through natural language commands. Available in both Python and Vercel implementations with comprehensive OAuth2 authentication and device management.
      -

    • MCP Spotify Server

      superseoworld
      A
      license
      B
      quality
      D
      maintenance
      Enables interaction with Spotify's music catalog via the Spotify Web API, supporting searches, artist information retrieval, playlist management, and automatic token handling.
      26
      22 npm
      23
      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.9/5.0

    Scored across 3 tools

    Disambiguation1/5

    All three tools — get_auth_status, health_check, and setup_instructions — serve nearly identical purposes related to authentication and server status. An agent would struggle to select the correct tool because they all provide information about setup or health with no distinct functional boundaries.

    Naming Consistency3/5

    All tools use snake_case with a 'spotify_' prefix, but the naming pattern is inconsistent: 'get_auth_status' follows a verb_noun pattern, while 'health_check' and 'setup_instructions' are noun_noun combinations, breaking the expected consistency.

    Tool Count1/5

    With only 3 tools, all dedicated to authentication and health, the server is vastly undersized for a Spotify service, which would typically require many tools for playback, search, queue management, etc. The count is far too low for the implied scope.

    Completeness1/5

    The tool surface covers only authentication and setup, missing core Spotify functionalities like play, pause, search, and playlist management. This is a severe gap that renders the server unable to perform any music-related tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources