1. Conduid
  2. Developer Tools
  3. Spotify
MCP server · Developer Tools

Spotify

MCP to connect your LLM with Spotify.

Unclaimed MIT last commit 7 months ago devtools
81Excellent

Scored 11 days ago · breakdown

About Spotify

Spotify is an MCP server published by varunneal in the Developer Tools category: mCP to connect your LLM with Spotify.

The repository has 614 stars and 131 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

Claude Code
claude mcp add spotify-mcp -- npx -y @novalux12/spotify-mcp
npx
npx -y @novalux12/spotify-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Spotify

Powered by Claude · Grounded in docs

I know everything about Spotify. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 4 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

spotify-mcp MCP server

MCP project to connect Claude with Spotify. Built on top of spotipy-dev's API.

[Notice March 2026]: Inactive project. Most PRs will not be merged.

Features

  • Start, pause, and skip playback
  • Search for tracks/albums/artists/playlists
  • Get info about a track/album/artist/playlist
  • Manage the Spotify queue
  • Manage, create, and update playlists

Demo

Configuration

Getting Spotify API Keys

Create an account on developer.spotify.com. Navigate to the dashboard. Create an app with redirect_uri as http://127.0.0.1:8080/callback. You can choose any port you want but you must use http and an explicit loopback address (IPv4 or IPv6).

See here for more info/troubleshooting. You may have to restart your MCP environment (e.g. Claude Desktop) once or twice before it works.

Locating MCP Config

For Cursor, Claude Desktop, or any other MCP-enabled client you will have to locate your config.

  • Claude Desktop location on MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json

  • Claude Desktop location on Windows: %APPDATA%/Claude/claude_desktop_config.json

Run this project with uvx

Add this snippet to your MCP Config.

{
  "mcpServers": {
    "spotify": {
      "command": "uvx",
      "args": [
        "--python", "3.12",
        "--from", "git+https://github.com/varunneal/spotify-mcp",
        "spotify-mcp"
      ],
      "env": {
        "SPOTIFY_CLIENT_ID": YOUR_CLIENT_ID,
        "SPOTIFY_CLIENT_SECRET": YOUR_CLIENT_SECRET,
        "SPOTIFY_REDIRECT_URI": "http://127.0.0.1:8080/callback"
      }
    }
  }
}

Run this project locally

Using UVX will open the spotify redirect URI for every tool call. To avoid this, you can run this project locally by cloning this repo:

git clone https://github.com/varunneal/spotify-mcp.git

Add it to your MCP Config like this:

"spotify": {
    "command": "uv",
    "args": [
      "--directory",
      "/path/to/spotify-mcp",
      "run",
      "spotify-mcp"
    ],
    "env": {
      "SPOTIFY_CLIENT_ID": YOUR_CLIENT_ID,
      "SPOTIFY_CLIENT_SECRET": YOUR_CLIENT_SECRET,
      "SPOTIFY_REDIRECT_URI": "http://127.0.0.1:8080/callback"
    }
  }

Troubleshooting

Please open an issue if you can't get this MCP working. Here are some tips:

  1. Make sure uv is updated. I recommend version >=0.54.
  2. If cloning locally, enable execution permisisons for the project: chmod -R 755.
  3. Ensure you have Spotify premium (needed for running developer API).

This MCP will emit logs to std err (as specified in the MCP) spec. On Mac the Claude Desktop app should emit these logs to ~/Library/Logs/Claude. On other platforms you can find logs here.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory /path/to/spotify-mcp run spotify-mcp

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

TODO

Unfortunately, a bunch of cool features have now been deprecated from the Spotify API. Most new features will be relatively minor or for the health of the project:

  • tests.
  • adding API support for managing playlists.
  • adding API support for paginated search results/playlists/albums.

PRs appreciated! Thanks to @jamiew, @davidpadbury, @manncodes, @hyuma7, @aanurraj, @JJGO and others for contributions.

README fetched from the repository 4 days ago. The original is authoritative.

Questions

About Spotify

How do I install Spotify?

Run claude mcp add spotify-mcp -- npx -y @novalux12/spotify-mcp, then add the server to your MCP client's configuration.

Is Spotify safe to use with an AI agent?

Its trust score is 81 out of 100 (excellent). It passes 4 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Spotify still maintained?

The last commit was 7 months ago and 26 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.