Spotify MCP Server (Express.js)

What is Spotify MCP Server (Express.js)?

This is a Model Context Protocol (MCP) server implementation that enables AI assistants to search tracks, retrieve artist information, and manage playlists through the Spotify API. It is built with Express.js and intended for developers building AI assistant integrations with Spotify.

How to use Spotify MCP Server (Express.js)?

Set up a Spotify Developer application, configure SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET, and SPOTIFY_REDIRECT_URI in a .env file, run npm install, then npm start. AI assistants interact via HTTP POST/GET endpoints to search music, get content details, or access user data after OAuth authentication.

Key features of Spotify MCP Server (Express.js)

• Search for tracks, artists, or albums via MCP endpoint
• Get detailed artist and track information by ID
• Get playlist information by ID
• Access user's top tracks, playlists, and saved tracks
• Spotify OAuth authentication flow for personalized data

Use cases of Spotify MCP Server (Express.js)

• An AI assistant helping users discover and search for music on Spotify
• An AI assistant retrieving detailed artist or track information on demand
• An AI assistant accessing a user's saved tracks, top tracks, or playlists

FAQ from Spotify MCP Server (Express.js)

What does this server do that a raw Spotify API client does not?

It implements the Model Context Protocol, allowing AI assistants to use structured endpoints for music search, content retrieval, and user data access without handling raw API calls directly.

What are the runtime requirements?

Node.js and npm. The server depends on Express.js and uses environment variables stored in a .env file for credentials.

Where do user credentials and data live?

Credentials live in a local .env file that should never be committed to version control. User authentication uses Spotify's OAuth flow; no user data is stored by the server itself.

What authentication and transport mechanisms are supported?

The server uses HTTP REST for transport and Spotify OAuth 2.0 for user authentication, with endpoints for login, OAuth callback, and token refresh.

Are there any known limitations?

The README does not state any explicit limits. All endpoints require proper authentication for user-specific data, and the server runs locally on http://localhost:3000.