# Spotify

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/pipeworx-io/mcp-spotify  
**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
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "spotify": {
    "command": "npx",
    "args": ["-y","spotify-5"]
  }
}
```

## Documentation & README

# @pipeworx/spotify

Spotify Web API MCP — catalog metadata via client_credentials OAuth.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.

## Tools

- `search(query, type?, market?, limit?, offset?)`
- `get_track(track_id, market?)`
- `get_artist(artist_id)`
- `get_album(album_id, market?)`
- `get_artist_top_tracks(artist_id, market?)`
- `get_audio_features(track_id)` — tempo, key, energy, danceability, etc.

## Auth

- **Platform key:** gateway env `PLATFORM_SPOTIFY_KEY`, format `client_id:client_secret`.
- **BYO:** `?_apiKey=client_id:client_secret` (colon-joined) after registering an app at https://developer.spotify.com/dashboard.

User-scope features (saved tracks, owned playlists) require the full Authorization Code flow and are out of scope.

## Data source

- Token: `https://accounts.spotify.com/api/token` (client_credentials grant)
- API: `https://api.spotify.com/v1/`

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "spotify": {
      "url": "https://gateway.pipeworx.io/spotify/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/spotify/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Spotify data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT