Skip to main content
Glama
markswendsen-code

@striderlabs/mcp-spotify

Related Servers

Alternatives to @striderlabs/mcp-spotify

No user-submitted related servers found.

    Related Servers

    • 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.
      12 npm
      9
      ISC
    • 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
    • A
      license
      A
      quality
      B
      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.
      47
      2
      MIT
    • 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
    • F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server that enables AI assistants to control Spotify playback and manage playlists.
      -
    • A
      license
      B
      quality
      B
      maintenance
      An MCP server that enables users to control Spotify playback, search music, and manage playlists through natural conversation. It is updated for the February 2026 Spotify Web API changes and supports full playlist CRUD operations.
      6
      8
      MIT

    TDQS

    A3.6/5.0

    Scored across 19 tools

    Disambiguation4/5

    The search_* tools are clearly distinguished by resource type (artists, albums, playlists, tracks), and playback/device/auth tools have distinct purposes. The only point of potential confusion is search_playlists (public search) vs get_playlists (user's library), but the descriptions clarify the boundary.

    Naming Consistency3/5

    The search_* prefix is consistent, but naming mixes bare verbs (play, pause), verb_noun (create_playlist, set_volume, get_devices), verb_prep_noun (add_to_playlist, remove_from_playlist), and a spotify_* prefix for auth tools. Multiple conventions coexist, making the pattern hard to predict, though each name remains readable.

    Tool Count4/5

    19 tools is on the heavier side, but Spotify's API spans search, playlists, playback control, devices, and authentication, so the count is justified by the domain breadth. Each tool earns its place and there is little redundancy, making the set feel appropriately scoped rather than bloated.

    Completeness3/5

    Core workflows work: search, play, pause, skip, volume, create/add/remove playlist items, device transfer, and auth. However, notable gaps exist — there is no way to list the tracks inside a playlist (making remove_from_playlist impractical without prior context), no playlist update/delete, and no seek, shuffle, or repeat controls.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues