Skip to main content
ClaudeWave
NovaLux12 avatar
NovaLux12

spotify-mcp-server

Ver en GitHub

The definitive Spotify MCP server — full non-deprecated Web API coverage, paginated everything, podcast-first, tested end to end

MCP ServersRegistry oficial0 estrellas0 forksTypeScriptMITActualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 8/26/2026
Install in Claude Code / Claude Desktop
Method: NPX · @novalux12/spotify-mcp
Claude Code CLI
claude mcp add spotify -- npx -y @novalux12/spotify-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "spotify": {
      "command": "npx",
      "args": ["-y", "@novalux12/spotify-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# SpotifyMCP

[![CI](https://github.com/NovaLux12/spotify-mcp-server/actions/workflows/ci.yml/badge.svg)](https://github.com/NovaLux12/spotify-mcp-server/actions/workflows/ci.yml)
[![npm version](https://img.shields.io/npm/v/@novalux12/spotify-mcp)](https://www.npmjs.com/package/@novalux12/spotify-mcp)
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
![Node](https://img.shields.io/badge/node-%3E%3D22.9-brightgreen)

An MCP server that wraps the Spotify Web API, letting AI assistants (like Claude) control playback, search the full catalog including podcasts and audiobooks, manage your library and playlists, and understand your listening taste.

## Why this one

Most Spotify MCP servers are thin wrappers. This one is built to be the default:

- **Complete API surface** — 94 tools covering every non-deprecated Spotify Web API endpoint callable with a standard developer token (playback, search, catalog, audiobooks, personalization, library, playlists, following, users) *plus* agent-grade extras most servers don't have: listening reports, library hygiene analysis, playlist merge/diff/DNA curation, a podcast session composer, named playback scenes, and an audiobook chapter copilot.
- **Honest about deprecations** — Spotify removed recommendations, related artists, audio features/analysis, genre seeds, and featured playlists from new apps. Servers still exposing those ship tools that fail at runtime; this one doesn't — and the few legacy endpoints it keeps (batch lookups, public user profiles) detect the 403 and explain it instead of crashing.
- **Safe by default** — every mutating tool accepts `dry_run=true` to preview exactly what would change without touching your account. Successful mutations return a receipt (post-write refetched state proving what landed), and a follow-up `verify_receipt` call re-checks it in later turns. Opt-in JSONL audit trail (`SPOTIFY_MCP_HISTORY=1`) logs every mutation for undo.
- **Scope-aware hiding** — write-capable modules whose scopes you didn't grant at auth time are hidden from the tool list entirely, instead of sitting there failing with 403 every time your agent tries them.
- **Right-sized surface** — `SPOTIFY_MCP_TOOLSETS=playback,catalog` trims the registered tools to a subset for hosts that cap tool counts; `SPOTIFY_MCP_ENABLE_TOOLS`/`SPOTIFY_MCP_DISABLE_TOOLS` fine-tune individual modules on top.
- **Self-diagnosing** — a CLI `doctor` command and an in-server `spotify_doctor` tool classify the real failure modes: missing/expired tokens, scope gaps between your grant and the exposed write tools, Premium-only gating, rate-limit cooldowns.
- **Tested** — full unit suite over the client (token refresh, rate limiting, pagination) and every tool handler, plus an end-to-end MCP protocol smoke test. Many alternatives have zero tests.
- **Paginated everything** — `fetch_all` on library and playlist listings walks every page (capped at 500 items) instead of silently truncating at one page of 50.
- **Podcasts are first-class** — episodes work everywhere: now-playing, queue, search-and-play, and a session composer that packs saved episodes into a commute-length listening block. Several competitors can't see podcasts at all.
- **Device-aware playback** — list devices, transfer playback, hand off mid-track to another Connect device, target any command at a specific device for multi-room setups, and recall named volume/device/repeat scenes.
- **Robust auth** — PKCE flow with silent refresh, persistent mode-600 token cache, headless paste-flow (`SPOTIFY_HEADLESS=1`) for servers and containers.

## Features

94 tools across 11 modules:

**Playback & devices (16 tools)** — now playing / currently-playing polls, play (by URI, or `play_from_search` to play straight from a name), pause, skip, previous, seek, volume, shuffle, repeat, queue view/add, device list, transfer playback, and `handoff` to move mid-track playback to another Spotify Connect device.

**Scenes & wind-down (6 tools)** — save named playback scenes (device + volume + shuffle/repeat + optional context) to a local sidecar and re-apply them in one call (`save_scene`, `list_scenes`, `delete_scene`, `apply_scene`); `schedule_wind_down` ramps the volume down to a floor over N minutes and then pauses; `cancel_wind_down` stops a running ramp.

**Search & catalog (20 tools)** — unified `search` across tracks/artists/albums/playlists/shows/episodes/audiobooks (limit capped at 10 per Spotify's Feb 2026 change) and `search_deep`, which walks past that cap server-side (up to 5 pages of 10 results per type, deduplicated); deep lookups for tracks, artists, artist albums, albums, album tracks, shows, show episodes, episodes, and your profile (`get_me`); batch `get_several_*` lookups for tracks, albums, artists, episodes, shows, audiobooks and chapters, plus artist top-tracks / available-markets — these were removed by Spotify's February 2026 Web API changes and fail with an explanatory message on newer app registrations (they still work with credentials from a grandfathered pre-Nov-2024 app).

**Audiobooks (7 tools)** — titles, chapters, chapter lookup, and your saved audiobooks (market-gated by Spotify to US/UK/CA/IE/NZ/AU); copilot extras: `list_all_chapters` (every chapter in one complete table, untruncated the way the Spotify app truncates), `jump_to_chapter` (resume the audiobook context at a numbered chapter), and `where_was_i` (which chapter you're on, how far in, time remaining).

**Personalization & reports (4 tools)** — top tracks and artists across three time ranges, recently played, and `listening_report`: compares your top tracks between two windows (rising / constant / fading) with an era histogram, discovery ratio, repeat overlap against recently played, and hour-of-day buckets.

**Library (14 tools)** — saved tracks/albums/shows/episodes with optional full pagination; save/remove/check partitioned by type to `/me/tracks|albums|shows|episodes(/contains)` (bare IDs), plus unified `/me/library` tools accepting any mix of track/album/show/episode/audiobook URIs in one request; `library_hygiene` flags incomplete albums and consolidation candidates over your liked tracks; genre tools (`library_genre_report`, `filter_by_genre`, `tag_management`) aggregate saved items by user-declared artist tags kept in a local sidecar.

**Playlists (16 tools)** — full CRUD plus item management (add/remove/reorder/replace), cover art retrieval and custom cover upload (`ugc-image-upload` scope required for upload), and `find_duplicates_in_playlist`; power ops: `merge_playlists` (dedupe + append/create), `diff_playlists` (fully paged A/B comparison with position-change detection), `overlap_playlists` (tracks shared across playlists); and `grow_playlist`, which proposes tracks using only your own listening data (co-occurrence across your other playlists — no deprecated recommendations endpoint).

**Following & freshness (5 tools)** — followed-artists list, follow-state checks, follow/unfollow, and `whats_new`: a personal new-releases radar derived from followed artists, with a local watermark so "everything since my last check" just works.

**Users (2 tools)** — any Spotify user's public profile and their public playlists (both removed by Spotify's February 2026 changes for newer app registrations; they degrade with a clear explanation and keep working for grandfathered credentials).

**Podcast sessions (2 tools)** — `plan_podcast_session` greedy-packs your saved episodes into a session of a given length (skipping fully played ones, resuming partially played ones at their position); `start_podcast_session` queues it on a device.

**Diagnostics & receipts (2 tools)** — `spotify_doctor`, an in-server diagnostic that checks token state, scope gaps versus the write tools actually exposed, Premium-only gating, and rate-limit cooldown without touching the network; and `verify_receipt`.

Every mutating tool accepts `dry_run=true` to preview exactly what would change before touching your account. Successful mutations append a **receipt** to their result — post-write refetched state proving what landed — and `verify_receipt` looks a receipt back up in a later turn. Set `SPOTIFY_MCP_HISTORY=1` to additionally log one JSONL line per mutation for an undo/audit trail. Write-capable modules whose scopes you didn't grant are hidden from the tool list entirely (scope-aware hiding), so agents never see commands that could only fail.

Also exposed: **MCP resources** — 11 fixed URIs (profile, player state, queue, top tracks/artists, recently played, playlists, saved albums/shows/episodes, rate-limit status), each available bare or with `?format=json` for raw machine-readable output, plus RFC-6570 templates (`spotify://playlist/{id}/tracks` paginated, `spotify://artist/{id}`, `spotify://artist/{id}/albums`, `spotify://album/{id}`, `spotify://show/{id}`, `spotify://episode/{id}`) with argument completions offered for show/episode IDs from your own library. And **10 prompt templates**: DJ set, mood playlist, taste summary, discovery alternative, playlist audit, listening recap, library migration, podcast catch-up, artist deep dive, and liked-songs triage.

## Requirements & limitations

- **Spotify Premium is required for playback control** (play, pause, skip, seek, volume, shuffle, repeat, queue, transfer). Free accounts can authenticate and use search/catalog/library/playlist tools, but every playback command will fail with a Premium-required error from Spotify.
- `fetch_all` pagination walks up to **500 items** per call (protects against runaway loops); beyond that, use `limit`/`offset` paging.
- Audiobook tools are market-gated by Spotify to US, UK, Canada, Ireland, New Zealand, and Australia.
- Spotify's developer mode allows up to 5 authorised users per app until extended quota is granted.
- **February 2026 platform caps, handled for you:** `/search` tops out at `limit=10` (default 5) — use `search_deep` to page past it; artist-albums pages 
ai-toolsclaudemcpmcp-servermodel-context-protocolspotifytypescript

Lo que la gente pregunta sobre spotify-mcp-server

¿Qué es NovaLux12/spotify-mcp-server?

+

NovaLux12/spotify-mcp-server es mcp servers para el ecosistema de Claude AI. The definitive Spotify MCP server — full non-deprecated Web API coverage, paginated everything, podcast-first, tested end to end Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-08-26.

¿Cómo se instala spotify-mcp-server?

+

Puedes instalar spotify-mcp-server clonando el repositorio (https://github.com/NovaLux12/spotify-mcp-server) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar NovaLux12/spotify-mcp-server?

+

Nuestro agente de seguridad ha analizado NovaLux12/spotify-mcp-server y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene NovaLux12/spotify-mcp-server?

+

NovaLux12/spotify-mcp-server es mantenido por NovaLux12. La última actividad registrada en GitHub es del 2026-08-26, con 2 issues abiertos.

¿Hay alternativas a spotify-mcp-server?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega spotify-mcp-server en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: NovaLux12/spotify-mcp-server
[![Featured on ClaudeWave](https://claudewave.com/api/badge/novalux12-spotify-mcp-server)](https://claudewave.com/repo/novalux12-spotify-mcp-server)
<a href="https://claudewave.com/repo/novalux12-spotify-mcp-server"><img src="https://claudewave.com/api/badge/novalux12-spotify-mcp-server" alt="Featured on ClaudeWave: NovaLux12/spotify-mcp-server" width="320" height="64" /></a>

Más MCP Servers

Alternativas a spotify-mcp-server