Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.XavierFabregat/spotify-mcp

NPM · @XAVIFABREGAT/SPOTIFY-MCP · SCANNED SEP 20

Conversational Spotify control from AI clients: play, queue, devices, playlists, and library.

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 827 tokens (~75/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 79% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.XavierFabregat/spotify-mcp server?

io.github.XavierFabregat/spotify-mcp runs locally as an npm package, launched with npx -y @xavifabregat/spotify-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @xavifabregat/spotify-mcp

# add to Claude Code
claude mcp add xavierfabregat-spotify-mcp -- npx -y @xavifabregat/spotify-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "xavierfabregat-spotify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@xavifabregat/spotify-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xavierfabregat-spotify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@xavifabregat/spotify-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add xavierfabregat-spotify-mcp -- npx -y @xavifabregat/spotify-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xavierfabregat-spotify-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@xavifabregat/spotify-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xavierfabregat-spotify-mcp --command npx --arg -y --arg @xavifabregat/spotify-mcp
# ~/.hermes/config.yaml
mcp_servers:
  xavierfabregat-spotify-mcp:
    command: "npx"
    args: ["-y", "@xavifabregat/spotify-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xavierfabregat-spotify-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@xavifabregat/spotify-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add xavierfabregat-spotify-mcp -t stdio -c npx -a -y @xavifabregat/spotify-mcp
// mcp.json
{
  "mcpServers": {
    "xavierfabregat-spotify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@xavifabregat/spotify-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@xavifabregat/spotify-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 108 packages
Packages resolved 108
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~827 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
authenticate ~44

Connects the user's Spotify account via OAuth. Opens a browser on this machine for approval and stores tokens locally. Use when other tools report you are not authenticated, or to switch accounts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

devices ~53

action=list shows available Spotify devices; action=transfer moves playback to a device by name or id.

NameTypeReqDescription
actionstringyes
devicestringDevice name (fuzzy) or id (action=transfer)

No output schema declared.

No examples provided.

get_playlist_items ~78

Lists the tracks in one of the user's own or collaborative playlists (Spotify no longer exposes other users' playlist contents). Accepts a playlist id, URI, or URL.

NameTypeReqDescription
offsetintegerPagination offset (default 0)
playliststringyesPlaylist id, spotify:playlist:… URI, or open.spotify.com URL

No output schema declared.

No examples provided.

get_playlists ~20

Lists the user's playlists with item counts and URIs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

library ~76

Saves, removes, or checks items in the user's Spotify library ('liked'). Works with any content URI: tracks, albums, artists (follow), shows, episodes. To save the current song, get its URI from now_playing first.

NameTypeReqDescription
actionstringyes
urisarrayyesSpotify URIs to act on

No output schema declared.

No examples provided.

modify_playlist ~125

action=create makes a new playlist (private by default); action=add_items appends track URIs to an existing playlist. Does not delete or remove anything.

NameTypeReqDescription
actionstringyes
descriptionstringNew playlist description (action=create)
namestringNew playlist name (action=create)
playliststringTarget playlist id/URI/URL (action=add_items)
publicbooleanMake the new playlist public (default false)
urisarrayTrack URIs to add (action=add_items)

No output schema declared.

No examples provided.

now_playing ~26

Current track, artist, album, progress, device, and shuffle/repeat state.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

play ~146

Plays music by free-text query (searches and starts the best match) or by Spotify URI. Handles "play some Radiohead", "play the album Kind of Blue", "play my Discover Weekly". Reports what it picked — relay that to the user so they can correct it.

NameTypeReqDescription
device_idstringTarget device id (see the devices tool)
querystringWhat to play, e.g. "Bill Evans" or "Kind of Blue". Required unless uri is given.
typestringWhat the query refers to (default: track)
uristringSpotify URI to play directly, e.g. from a previous search result

No output schema declared.

No examples provided.

playback ~90

Transport controls for the active playback: pause, resume, next, previous, seek (value = seconds), volume (value = 0-100), shuffle (value = on/off), repeat (value = off/context/track).

NameTypeReqDescription
actionstringyes
valuenumber|stringseek: seconds · volume: 0-100 · shuffle: on/off · repeat: off/context/track

No output schema declared.

No examples provided.

queue ~65

action=add queues a track by query or URI; action=list shows what's playing and up next.

NameTypeReqDescription
actionstringyes
querystringTrack to queue by name (action=add)
uristringTrack URI to queue (action=add)

No output schema declared.

No examples provided.

search ~104

Searches the Spotify catalog. Use when the user wants options to choose from; for a direct 'play X' request, prefer the play tool. Results include URIs usable with play, queue, playlists, and library. Max 10 results per type (API limit).

NameTypeReqDescription
limitintegerResults per type, 1-10 (default 5)
querystringyesSearch text
typesarrayResult types to include (default: track)

No output schema declared.

No examples provided.

Common questions

What is the io.github.XavierFabregat/spotify-mcp server?

io.github.XavierFabregat/spotify-mcp is listed in the public MCP registry as io.github.XavierFabregat/spotify-mcp. Conversational Spotify control from AI clients: play, queue, devices, playlists, and library. This page covers its npm package (@xavifabregat/spotify-mcp).

Is the io.github.XavierFabregat/spotify-mcp server safe to use?

io.github.XavierFabregat/spotify-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.XavierFabregat/spotify-mcp server expose?

io.github.XavierFabregat/spotify-mcp exposes 11 tools: authenticate, play, playback, now_playing, queue, and 6 more. Their descriptions and schemas cost roughly 827 tokens of context every time the server is loaded.

Is the io.github.XavierFabregat/spotify-mcp server still maintained?

io.github.XavierFabregat/spotify-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.XavierFabregat/spotify-mcp server under?

io.github.XavierFabregat/spotify-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.