Log inSubmit server
Spotify logo

Spotify

Queries Spotify catalog metadata through MCP using client-credentials OAuth.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Spotify

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "spotify-5": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-spotify"
      ],
      "env": {
        "PLATFORM_SPOTIFY_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Spotify MCP server exposes Spotify Web API catalog metadata through MCP tools. It authenticates with the client_credentials OAuth flow and supports search, track, artist, album, top-track, and audio-feature lookups. Use the hosted Pipeworx endpoint for remote MCP access, or run the npm package locally over stdio. It does not support user-scoped data such as saved tracks or owned playlists.

Use cases

  • Search Spotify’s catalog from an AI client
  • Retrieve track, artist, or album metadata
  • Inspect audio features for a track
  • Find an artist’s top tracks by market
  • Run Spotify catalog lookups through a local stdio process

Key features

  • Spotify catalog search with filtering and pagination
  • Track, artist, and album metadata lookup
  • Artist top-track retrieval by market
  • Audio feature retrieval including tempo and energy
  • Client-credentials OAuth authentication
  • Hosted gateway and local stdio deployment

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · @pipeworx/mcp-spotify (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads525Package downloads in the last 30 days.
Last commit26d agoMost recent push to the default branch.

How Spotify works

What the Spotify MCP server does

The Spotify MCP server gives an MCP client access to selected Spotify Web API catalog endpoints. It is intended for metadata lookups rather than account management or playback control. Available operations include searching the catalog, retrieving tracks, artists, and albums, finding an artist’s top tracks, and reading audio attributes such as tempo, key, energy, and danceability.

Search accepts a query and optional type, market, limit, and offset values. Track and album lookups can also take a market, while artist lookups require an artist ID. The top-tracks operation takes an artist ID and market, and audio features takes a track ID.

How it works

Authentication uses Spotify’s client_credentials grant. The service obtains a token from Spotify’s accounts endpoint and sends requests to the Spotify Web API. This flow provides access to catalog data without a Spotify user session.

You can connect through the hosted Pipeworx MCP endpoint at https://gateway.pipeworx.io/spotify/mcp. A pack endpoint exposes the Spotify tools along with Pipeworx shared meta-tools, including ask_pipeworx, discover_tools, search_within, and memory-related tools. The full gateway is also available when you want all packs listed directly. Both gateway URLs use the same underlying gateway, while the local package exposes only the Spotify pack tools.

For direct HTTP use, Pipeworx provides tool endpoints such as POST /v1/tools/spotify_search. Tools can also be inspected through the gateway’s HTTP API.

Setup and configuration

For a remote MCP connection, add the hosted endpoint to an MCP client configuration. The README names Claude Desktop, Cursor, and Windsurf as compatible clients. The local option runs @pipeworx/mcp-spotify with npx and communicates over stdin and stdout, avoiding a Pipeworx account and an extra gateway network hop.

Gateway authentication can use the PLATFORM_SPOTIFY_KEY environment value, formatted as client_id:client_secret. Alternatively, a caller can provide the same colon-joined credentials through the _apiKey query parameter after creating an application in the Spotify Developer Dashboard. The package documentation does not list additional environment variables.

Tools and capabilities

The pack provides these catalog operations:

  • search for catalog queries with optional filtering and pagination
  • get_track for track metadata
  • get_artist for artist metadata
  • get_album for album metadata
  • get_artist_top_tracks for an artist’s top tracks by market
  • get_audio_features for track-level musical attributes

The gateway’s ask_pipeworx tool can route a plain-language question to an appropriate tool and populate its arguments. That routing is available from either the Spotify pack endpoint or the full Pipeworx gateway.

Limitations and notes

This Spotify MCP server covers catalog metadata through client-credentials authentication. Features that require a Spotify user authorization, including saved tracks and owned playlists, are explicitly outside its scope. The remote pack endpoint lists shared gateway tools in addition to the Spotify tools, so its tool count is larger than the six pack operations. The local stdio process lists only the pack’s own tools and does not provide Pipeworx-wide routing.

The package is released under the MIT license. The gateway and local package use the same source and expose the same Spotify-specific operations, but they differ in connection method and whether shared gateway tools are available.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Spotify

Spotify is an MCP server that connects AI clients to the Spotify Web API for catalog metadata. Its main tools search the catalog, retrieve track, artist, and album details, list an artist’s top tracks, and return audio features such as tempo, key, energy, and danceability.

Run `npx -y @pipeworx/mcp-spotify` or add that command to an MCP client configuration. This starts the local stdio package without a Pipeworx account. You can instead configure the hosted `https://gateway.pipeworx.io/spotify/mcp` endpoint.

Use Spotify client-credentials OAuth with `client_id:client_secret` credentials. For the gateway, set `PLATFORM_SPOTIFY_KEY`, or pass the colon-joined value as `_apiKey` after registering an application in the Spotify Developer Dashboard.

Yes, Cursor is named as a supported MCP client in the setup instructions. Configure it with the hosted Pipeworx MCP URL, or run the package locally through the documented `npx` stdio command.

No, saved tracks and owned playlists are not supported. Those features require Spotify’s full Authorization Code flow, while this server uses client-credentials OAuth for catalog metadata.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSpotify AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/spotify-5?style=directory)](https://allmcps.com/mcp/spotify-5)
HTML Embed
<a href="https://allmcps.com/mcp/spotify-5"><img src="https://allmcps.com/api/badge/spotify-5?style=directory" alt="Spotify on AllMCPs" /></a>