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.markswendsen-code/spotify

NPM · @STRIDERLABS/MCP-SPOTIFY

MCP server for Spotify - let AI agents control playback, search music, and manage playlists

−1 this week 84 Trust /100

Last scanned (3 hours ago)

Scores higher than 81% of npm servers

Category Entertainment and Games

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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 752 tokens (~50/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
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.

  • 4 Nov 26 0
    • Stability: 0.97 → pass security
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 23 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 20 Oct 26 −1
    • Stability: pass → 0.97 functional
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 5 Nov 2026 · Analysed npm/@striderlabs/mcp-spotify@0.1.0

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 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~752 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
add_to_queue ~66

Add a track to the Spotify playback queue.

NameTypeReqDescription
device_idstring–Target device ID (optional)
uristringyesSpotify track URI (e.g., spotify:track:4iV5W9uYEdYUVa79Axb7Rh)

No output schema declared.

No examples provided.

get_playback ~33

Get the current Spotify playback state — what's playing, track info, device, volume, progress, shuffle/repeat mode.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_playlists ~51

Get the current user's Spotify playlists.

NameTypeReqDescription
limitnumber–Number of playlists to return (1-50, default: 50)
offsetnumber–Pagination offset (default: 0)

No output schema declared.

No examples provided.

get_recently_played ~41

Get the user's recently played tracks on Spotify.

NameTypeReqDescription
limitnumber–Number of tracks to return (1-50, default: 20)

No output schema declared.

No examples provided.

login ~35

Initiate Spotify OAuth login flow. Opens the browser for the user to authorize the app. Requires SPOTIFY_CLIENT_ID to be set.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

logout ~15

Logout from Spotify and clear stored credentials.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pause ~24

Pause Spotify playback.

NameTypeReqDescription
device_idstring–Target device ID (optional)

No output schema declared.

No examples provided.

play ~121

Start or resume Spotify playback. Can play a specific track, album, artist, or playlist URI, or resume current playback if no URI is provided.

NameTypeReqDescription
device_idstring–Target device ID (optional, uses active device by default)
position_msnumber–Start position in milliseconds (optional)
uristring–Spotify URI to play (e.g. spotify:track:4iV5W9uYEdYUVa79Axb7Rh, spotify:album:..., spotify:artist:..., spotify:playlist:...)

No output schema declared.

No examples provided.

play_playlist ~88

Play a specific Spotify playlist by its ID or URI.

NameTypeReqDescription
device_idstring–Target device ID (optional)
playlist_idstringyesSpotify playlist ID or full URI (e.g., 37i9dQZF1DXcBWIGoYBM5M or spotify:playlist:37i9dQZF1DXcBWIGoYBM5M)

No output schema declared.

No examples provided.

search ~87

Search Spotify for tracks, albums, artists, and/or playlists.

NameTypeReqDescription
limitnumber–Number of results per type (1-50, default: 10)
querystringyesSearch query (e.g., "The Beatles", "Bohemian Rhapsody Queen")
typearray–Types to search for (default: ["track", "album", "artist"])

No output schema declared.

No examples provided.

seek ~46

Seek to a specific position in the currently playing track.

NameTypeReqDescription
device_idstring–Target device ID (optional)
position_msnumberyesPosition to seek to, in milliseconds

No output schema declared.

No examples provided.

set_volume ~42

Set the playback volume.

NameTypeReqDescription
device_idstring–Target device ID (optional)
volume_percentnumberyesVolume level from 0 to 100

No output schema declared.

No examples provided.

skip_next ~30

Skip to the next track in the queue.

NameTypeReqDescription
device_idstring–Target device ID (optional)

No output schema declared.

No examples provided.

skip_previous ~43

Skip to the previous track. If more than 3 seconds into the current track, restarts it instead.

NameTypeReqDescription
device_idstring–Target device ID (optional)

No output schema declared.

No examples provided.

status ~30

Check Spotify connection and authentication status. Use this to see if the user is logged in and what account is connected.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.markswendsen-code/spotify MCP server?

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

npm · @striderlabs/mcp-spotify

# add to Claude Code
claude mcp add markswendsen-code-spotify -- npx -y @striderlabs/mcp-spotify
Common questions

What is the io.github.markswendsen-code/spotify MCP server?

io.github.markswendsen-code/spotify is an MCP server listed in the public MCP registry as io.github.markswendsen-code/spotify. MCP server for Spotify - let AI agents control playback, search music, and manage playlists. This page covers its npm package (@striderlabs/mcp-spotify).

Is the io.github.markswendsen-code/spotify MCP server safe to use?

io.github.markswendsen-code/spotify scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.markswendsen-code/spotify MCP server expose?

io.github.markswendsen-code/spotify exposes 15 tools: status, login, logout, get_playback, play, and 10 more. Their descriptions and schemas cost roughly 752 tokens of context every time the server is loaded.

Is the io.github.markswendsen-code/spotify MCP server still maintained?

io.github.markswendsen-code/spotify is still listed as active in the MCP registry. We last reached this channel on 5 November 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.markswendsen-code/spotify MCP server under?

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