Vulpes Spotify MCP Server

MCP server for Spotify integration

Local serverstdio

What is the Vulpes Spotify MCP MCP server?

If you already use Vulpes Spotify MCP, the vulpes spotify mcp mcp server is the piece that lets your assistant work with it directly. MCP server for Spotify integration.

What the server does

A Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with Spotify, allowing them to search for and play tracks.

  • Search for tracks by artist, title, or any query
  • Play tracks directly on your active Spotify device
  • Get information about your currently playing track
  • Find available Spotify playback devices
  • Combined search-and-play functionality
  • List user's Spotify playlists

Installation

The server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • spotify-search — Search for tracks by query
  • spotify-play — Play a specific track by ID or URI
  • spotify-currently-playing — Get information about the currently playing track
  • spotify-devices — List available Spotify playback devices
  • spotify-search-and-play — Search for a track and automatically play the top result
  • spotify-playlists — Get a list of the user's Spotify playlists
  • spotify-playlist-tracks — Get tracks from a specific playlist
  • spotify-play-playlist — Play a specific playlist (with optional shuffle)
  • spotify-find-playlist — Find a playlist by name and play it (recommended for AI use)

Credentials and setup notes

Configuration is passed through the environment: SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, SPOTIFY_REDIRECT_URI, SPOTIFY_REFRESH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js (v16+) - Spotify Developer Account - Spotify Premium account (for playback functionality) - An MCP-compatible client (e.g., Claude Desktop)

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Vulpes Spotify MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Vulpes Spotify MCP's toolset — spotify-search, spotify-play, spotify-currently-playing and 6 more — is a fair guide to whether it matches your workflow. It is maintained by ejfox; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Vulpes Spotify MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
spotify-searchSearch for tracks by query
spotify-playPlay a specific track by ID or URI
spotify-currently-playingGet information about the currently playing track
spotify-devicesList available Spotify playback devices
spotify-search-and-playSearch for a track and automatically play the top result
spotify-playlistsGet a list of the user's Spotify playlists
spotify-playlist-tracksGet tracks from a specific playlist
spotify-play-playlistPlay a specific playlist (with optional shuffle)
spotify-find-playlistFind a playlist by name and play it (recommended for AI use)

How to install the Vulpes Spotify MCP MCP server

{
     "mcpServers": {
       "spotify": {
         "command": "node",
         "args": ["/absolute/path/to/vulpes-spotify-mcp/dist/index.js"],
         "env": {
           "SPOTIFY_CLIENT_ID": "your_client_id",
           "SPOTIFY_CLIENT_SECRET": "your_client_secret",
           "SPOTIFY_REDIRECT_URI": "http://localhost:8888",
           "SPOTIFY_REFRESH_TOKEN": "your_refresh_token"
         }
       }
     }
   }

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js (v16+) - Spotify Developer Account - Spotify Premium account (for playback functionality) - An MCP-compatible client (e.g., Claude Desktop)
VariableDescriptionRequired
SPOTIFY_CLIENT_IDConfiguration value read at startup.Optional
SPOTIFY_CLIENT_SECRETCredential the server authenticates with.Yes
SPOTIFY_REDIRECT_URIFilesystem location the server is allowed to use.Optional
SPOTIFY_REFRESH_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Vulpes Spotify MCP to spotify-search.
  • Use Vulpes Spotify MCP to spotify-play.
  • Use Vulpes Spotify MCP to spotify-currently-playing.

Frequently asked questions

It connects Vulpes Spotify MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (spotify-search, spotify-play, spotify-currently-playing, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Vulpes Spotify MCP directly.