Spotify MCP Server

Name: Spotify MCP Server
Author: Shrau1711

@Shrau1711

关于 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.

#spotify #mcp #ai-assistant

基本信息

分类

媒体与设计

运行时

python

传输方式

stdio

发布者

Shrau1711

配置

暂无标准配置

该服务器的 README 中没有可解析的 MCP 配置块，请前往代码仓库查看安装说明。

代码仓库

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

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.