Spotify MCP Server

Overview

The Spotify MCP Server is a lightweight, standard‑in/standard‑out bridge that lets AI assistants such as Claude access Spotify data without the need for a web‑based callback flow. By exposing a small set of tools over the MCP interface, developers can query Spotify on demand from within conversational agents, turning a typical web‑auth process into a simple command that runs locally. This eliminates the friction of configuring OAuth redirect URLs and allows quick prototyping or internal tooling that requires Spotify integration.

At its core, the server authenticates with the Spotify Web API using a client‑credentials flow. Once authenticated, it offers one primary tool—GetUserPlaylists—which retrieves the list of playlists belonging to a specified user ID. The tool accepts a single string argument and returns a JSON payload containing playlist metadata such as names, IDs, track counts, and cover images. Because the server runs as a separate process, it can be started once per development session and reused by multiple AI clients without repeated authentication overhead.

Key features include:

• Zero‑config OAuth: The server accepts any redirect URI, so developers can skip the usual web callback setup.
• Portable .NET 8.0 build: A single executable that runs on any platform supporting .NET, simplifying deployment in CI/CD pipelines or local workstations.
• MCP‑ready: The server adheres to the Model Context Protocol, exposing tools in a JSON schema that AI assistants can discover automatically.
• Extensible toolset: While the current release ships with a single playlist query, the architecture allows adding more Spotify endpoints (e.g., track search, user profile) with minimal effort.

Typical use cases involve building conversational music assistants that can fetch a user’s playlists on request, creating data pipelines that aggregate playlist statistics for analytics dashboards, or enabling AI‑powered music recommendation workflows in internal tooling. By integrating this server into an MCP‑compatible environment, developers can embed Spotify data retrieval directly into natural language conversations, reducing latency and simplifying the user experience. The standout advantage is its simplicity—no need for a running web server or complex OAuth dance—making it an ideal starting point for rapid experimentation with music data in AI applications.