Skip to main content
Glama
Spotify Data MCP Server

Spotify Data MCP Server

Related Servers

Alternatives to Spotify Data MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to retrieve per-track play counts for tracks, albums, artists, and playlists from links or URIs, along with monthly listeners, followers, world rank, top cities, and optional daily stream history.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to fetch music artist, album, and track metadata, search tracks, discover similar artists, and list top tracks, tags, charts, and user listening stats through MCP tools.
      74 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      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.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI assistants to control Spotify Premium accounts by searching music, managing playback and devices, handling queues, creating and editing playlists, and browsing or modifying the library.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to search Spotify's track catalog and retrieve the connected user's recently played tracks through natural language tool calls.
      MIT
    • 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.
      -

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation3/5

    The track tools overlap heavily: get_tracks already returns play counts by default and insights via include_insights, which largely subsumes get_track_play_count and get_track_insights. Similarly get_artist_overview absorbs much of get_artists_stats and get_artist_insights. Descriptions do help (batch vs. single, 'fastest way to compare streams'), but an agent still has to reason about which of several near-duplicate paths to take.

    Naming Consistency4/5

    Most tools follow a clear get_<resource> pattern (get_tracks, get_album, get_playlist, get_chart), with two outliers: 'search' (bare verb, no noun) and 'isrc_lookup' (noun_verb reversed). Singular/plural switching (get_tracks vs. get_track_play_count) is slightly irregular but readable and intentional.

    Tool Count5/5

    Twelve tools is well within the sweet spot and each maps to a concrete Spotify data concept (tracks, artists, albums, playlists, charts, ISRC). Nothing feels padded except arguably the redundant track/artist variants, but the count itself is well scoped.

    Completeness4/5

    The surface covers the analytics domain well: discovery via search and isrc_lookup, batch and single lookups across tracks/artists/albums/playlists, plus charts. Minor gaps remain — albums are single-only with no batch counterpart, and there is no way to list an artist's full discography or enumerate playlists, but these are workaroundable.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data