# Spotify [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pipeworx-io/mcp-spotify  
**GitHub Stars:** 0  
**npm Downloads (last month):** 525  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/spotify-5

## Description
Spotify MCP — Web API via client_credentials OAuth

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "spotify": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-spotify"],
    "env": {
      "PLATFORM_SPOTIFY_KEY": ""
    }
  }
}
```

**Requires environment variables:** `PLATFORM_SPOTIFY_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/spotify-5/readme_