MCP.so
Sign In

Spotify MCP Server

@Shrau1711

About Spotify MCP Server

A server that enables AI assistants to interact with Spotify via the Model Context Protocol (MCP). It allows fetching current playback, controlling playback, and accessing user playlists.

Basic information

Category

Media & Design

Runtime

python

Transports

stdio

Publisher

Shrau1711

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Spotify MCP Server?

Spotify MCP Server is a Flask-based MCP server that integrates with the Spotify Web API to control playback, manage volume, retrieve playlists, and execute custom commands via MCP. It is intended for developers who want to automate or extend Spotify functionality through MCP-compatible clients.

How to use Spotify MCP Server?

Deploy the Flask server and authenticate via Spotify OAuth using the /login and /callback endpoints. Then send HTTP requests to endpoints such as /play, /pause, /next, /previous, /volume?volume=XX, /current-song, /playlists, or /mcp-command?command=....

Key features of Spotify MCP Server

  • Authenticate with Spotify via OAuth
  • Control playback (Play/Pause/Next/Previous)
  • Adjust volume to a specified level
  • Fetch currently playing song
  • Retrieve user playlists
  • Execute MCP commands like play

Use cases of Spotify MCP Server

  • Build a voice‑controlled music assistant using MCP
  • Automate playlist management and playback in smart home setups
  • Integrate Spotify playback into custom dashboards or bots
  • Extend MCP‑compatible agents with music control capabilities

FAQ from Spotify MCP Server

How does authentication work?

The server uses Spotify OAuth. Start at the /login endpoint, which redirects to Spotify for authorization; after approval, Spotify redirects to /callback to complete the flow.

What are the runtime dependencies?

The server is built with Flask and requires Python. It communicates with the Spotify Web API over HTTP; no additional runtime is specified.

Where does user data live?

User data (playlists, current song) is fetched live from Spotify’s servers via the Web API. No local data storage is documented.

Does the server support any transport besides HTTP?

No. All endpoints are HTTP‑based; no alternative transports (e.g., WebSocket, stdio) are mentioned.

Are there any known limits or rate limits?

The README does not specify any server‑side limits. However, the underlying Spotify Web API enforces its own rate limits, which apply to applications using this server.

Comments

More Media & Design MCP servers