Skip to main content
Glama
gupta-kush

spotify-mcp

by gupta-kush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to spotify-mcp

No user-submitted related servers found.

    Related Servers

    • Spotify MCP Server

      llyfn
      A
      license
      B
      quality
      C
      maintenance
      MCP server for the Spotify Web API — gives Claude and other AI assistants tools to search music, control playback, manage playlists, library, and podcasts.
      59
      MIT

    • spotify-direct-mcp

      thejaredchapman
      F
      license
      Not graded
      quality
      D
      maintenance
      A FastMCP server that exposes Spotify's catalog and user context as tools for Claude, enabling track search, audio features, artist discography, recommendations, currently playing, and playlist creation.
      -

    • mcp-spotify

      obrien-matthew
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Spotify that enables playlist building and music discovery through 19 tools, allowing LLM agents to search tracks/artists/albums, manage playlists, control playback, and access personal listening data.
      20
      MIT

    • MCP PLAYLIST SERVER

      alee2602
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides intelligent playlist curation tools using Spotify track data and audio feature analysis. It enables AI assistants to create mood-based playlists, find similar songs, analyze audio characteristics, and curate personalized music collections.
      -

    • spotify-library-mcp

      oliver-virt
      A
      license
      B
      quality
      B
      maintenance
      Enables you to manage your personal Spotify library from Claude or a CLI, including organizing playlists, merging and deleting playlists, saving tracks, searching with artist verification, and querying top tracks, artists, and recently played items.
      27
      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 93 tools

    Disambiguation3/5

    Several tools have overlapping boundaries, such as spotify_status vs spotify_now_playing, spotify_play vs spotify_resume, spotify_cleanup_playlist vs spotify_deduplicate_playlist, and spotify_playlist_diff vs spotify_playlist_compare. Descriptions provide enough detail to distinguish most tools with careful reading, but the large number of closely related playlist and discovery functions creates genuine misselection risk.

    Naming Consistency4/5

    The overwhelming majority follow a consistent spotify_verb_noun pattern (e.g., spotify_get_devices, spotify_create_playlist, spotify_skip_next). There are a few noun-phrase exceptions like spotify_playlist_analysis, spotify_playlist_vibe, and spotify_library_stats, but these are still readable and do not break the overall convention.

    Tool Count1/5

    93 tools is extreme for any MCP server, far beyond the 3–15 well-scoped range. While the Spotify API is broad, this surface would overwhelm agents and makes selection, navigation, and maintenance unnecessarily difficult. The count alone is a strong negative signal.

    Completeness3/5

    Core playback, library, playlist, and discovery workflows are well covered, and custom curation tools add significant value. However, there are notable omissions like removing tracks from a playlist, deleting/unfollowing playlists, unsaving tracks/albums/episodes/shows, and unfollowing artists/users, which create dead ends in standard lifecycle flows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources