Skip to main content
Glama
superseoworld

MCP Spotify Server

by superseoworld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to MCP Spotify Server

No user-submitted related servers found.

    Related Servers

    • Spotify MCP

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

    • Spotify API MCP

      fisknils
      F
      license
      A
      quality
      D
      maintenance
      Enables interaction with Spotify through OAuth 2.0 authentication, supporting search for tracks/artists/albums/playlists, user profile access, and playlist management including creation and adding tracks.
      6
      -

    • spotify-mcp-server

      thebigredgeek
      A
      license
      C
      quality
      D
      maintenance
      Enables natural language control of Spotify, including search, playback, and device management, with robust error handling and automatic token refresh.
      3
      37 npm
      MIT

    • Spotify MCP Server

      akarnik23
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Spotify's music catalog through natural language conversations. Search for tracks and artists, get recommendations, explore playlists, and browse artist discographies using the Spotify Web API.
      -

    • 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
    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 26 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources (e.g., albums, artists, playlists), but there is some overlap between get_playlist_items and get_playlist_tracks, which could cause confusion as both retrieve playlist content. The descriptions clarify that get_playlist_tracks focuses on tracks specifically, while get_playlist_items is more general, but the distinction is subtle and might lead to misselection.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, with all tools using snake_case and starting with verbs like 'get', 'add', 'remove', or 'modify'. This predictability makes it easy for agents to understand and navigate the toolset without confusion.

    Tool Count2/5

    With 26 tools, the count feels excessive for a Spotify API server, as many tools could be consolidated (e.g., multiple 'get' tools for similar resources). This bloat may overwhelm agents and complicate decision-making, indicating a lack of streamlined design for the domain.

    Completeness5/5

    The toolset provides comprehensive coverage of the Spotify domain, including CRUD operations for playlists (add, remove, modify), extensive catalog access for albums, artists, tracks, and audiobooks, and features like search, recommendations, and user-specific data. No obvious gaps exist, ensuring agents can handle a wide range of Spotify-related tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources