markandeyay/spotify-mcp

Remote MCP server linking Claude to Spotify, with smart playlist, listening-trend, and library analysis.

About spotify-mcp

A remote MCP server for Spotify with brokered OAuth and a server-side intelligence layer. Add it to Claude as a custom connector, log in to Spotify once, and every tool works. No local install, no JSON editing, no per-user Spotify developer app.

1. In Claude, go to Settings, then Connectors, then "Add custom connector". 2. Paste this URL:

3. Claude opens a Spotify login page. Approve it. 4. Ask Claude to call getinitialcontext to confirm the connection.

You authenticate once. The server encrypts your Spotify tokens at rest and refreshes them transparently.

Note: the Spotify app behind the hosted server runs in Development Mode, which Spotify caps at 5 authorized users. Your Spotify account email must be allowlisted by the owner before you can log in. If you are not on the list, self-host instead.

You need: a Spotify developer app, a free Neon Postgres database, and a free Render web service (Fly.io or Railway work too).

1. Spotify dashboard: create an app. Add https:///callback as a redirect URI. Note the client ID and secret. The app owner needs active Premium for the playback tools, and each user's Spotify email must be added under User Management while in Development Mode (5 max). 2. Neon: create a project and copy the connection string. 3. Render: create a web service from this repo. - Build command: npm ci --include=dev && npm run build && npm run db:migrate (the --include=dev matters: Render sets NODEENV=production, which otherwise skips the dev dependencies the build needs; migrations run against DATABASEURL on each deploy and are idempotent) - Start command: n

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/markandeyay--spotify-mcp.html)

Related MCP servers