Skip to main content
Glama
abenke

Spotify MCP

by abenke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Spotify MCP

No user-submitted related servers found.

    Related Servers

    • spotify-mcp

      raksix
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of Spotify playback via the official Web API, including search/play, pause, skip, volume, queue, and device management.
      81 npm
      1
      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
      -

    • 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
      7 npm
      23
      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 Streamable MCP Server

      iceener
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables control of Spotify through natural language by searching the catalog, managing playback and devices, controlling playlists, and managing saved songs. Includes OAuth authentication and streamable HTTP transport for remote connectivity.
      8 npm
      79
      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

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose: authentication, user info, search, playback status, and playlist management. No overlapping functionality, and descriptions clearly differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_playlist, get_currently_playing, add_tracks_to_playlist), making the API predictable and easy to navigate.

    Tool Count5/5

    10 tools provide a well-scoped set for a music assistant: authentication, user profile, search, playback info, and playlist CRUD. This covers essential interactions without being excessive or insufficient.

    Completeness4/5

    Core workflows are covered (auth, search, playlist management). Minor gaps exist (e.g., removing tracks from playlists, updating playlist metadata, playback control), but most agents will find the set sufficient for common tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources