Skip to main content
Glama
LLMTooling

Spotify MCP Server

by LLMTooling
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Spotify MCP Server

No user-submitted related servers found.

    Related Servers

    • spotifyMCP

      real-kijmoshi
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling Spotify playback, managing playlists, searching music, and accessing library features through any MCP-compatible AI client. Provides 34 tools for full Spotify integration.
      -

    • spotify-mcp-server

      freddy24-7
      F
      license
      A
      quality
      D
      maintenance
      Exposes Spotify controls as MCP tools for playback, playlist management, and AI playlist generation; includes a web app and supports multi-user profiles.
      14
      -

    • 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-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.
      60 npm
      1
      MIT

    • Spotify MCP Server (Python)

      argotdev
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Spotify through MCP, providing tools for searching tracks, artists, albums, playlists, and accessing user data like top tracks and recently played.
      -
    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.4/5.0

    Scored across 51 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with very specific actions and targets. Even though there are many tools for retrieving individual attributes of the current track, their names and descriptions unambiguously indicate what each returns.

    Naming Consistency5/5

    All tools follow the consistent pattern 'spotify_verb_noun' (e.g., spotify_get_track_name, spotify_set_volume). There are no mixed conventions or deviations.

    Tool Count2/5

    With 51 tools, the set is overly large for the domain. Many granular getters (e.g., spotify_get_track_name, spotify_get_track_id) could be consolidated into fewer tools, making the surface bloated and harder to navigate.

    Completeness3/5

    The set covers playback control, current state, search, and basic library management well, but lacks playlist creation/modification and other common operations like following artists or user profile retrieval. Some gaps remain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources