Skip to main content
Glama
walter-kai

Spotify MCP Server

by walter-kai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Spotify MCP Server

No user-submitted related servers found.

    Related Servers

    • SpotifyMCP

      NovaLux12
      A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to control Spotify playback, search the full catalog including podcasts and audiobooks, manage libraries and playlists, and understand listening taste.
      500
      185 npm
      1
      MIT

    • Spotify MCP Server

      Yonsn76
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Spotify playback, search for music, manage playlists, and access library information through the Spotify API. Requires Spotify Premium for playback control features.
      4
      -

    • Spotify MCP Server

      ElBeldu
      F
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to control Spotify playback, search the catalog, and manage playlists and liked songs through natural language. Supports reading currently playing tracks, queues and devices, plus play, pause, skip, queueing, volume control, and playlist creation and editing.
      30
      -
    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 32 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, making the set easy to navigate. A few have minor boundary risk (spotify_play vs spotify_transfer_playback vs spotify_open, and singular spotify_get_playlist vs plural spotify_get_playlists), but descriptions clearly differentiate them.

    Naming Consistency5/5

    Every tool uses the same spotify_ prefix with consistent snake_case, mostly verb_noun (spotify_create_playlist, spotify_remove_saved_tracks) and clean verb-only playback controls (spotify_play, spotify_pause). The pattern is predictable throughout.

    Tool Count3/5

    At 32 tools the surface is heavy and sits just past the range where a set becomes unwieldy for an agent to select from. Each tool does earn its place given Spotify's breadth, so it's borderline rather than bloated.

    Completeness4/5

    The set covers playback control, full playlist CRUD, library save/remove, follow/unfollow, search, and user data retrieval rather thoroughly. Minor gaps exist (queue management, podcast/episode tools, album/artist detail retrieval), but core workflows are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources