Spotify

What is Spotify?

A remote Model Context Protocol (MCP) server that provides full coverage of the Spotify Web API, enabling AI assistants to interact with Spotify. Built with Bun, Hono, and Supabase, it requires no local installation for end users.

How to use Spotify?

Add the server as a custom connector in Claude.ai using the URL https://sptfy-mcp.online/mcp, or add it to any MCP client supporting Streamable HTTP by including the same URL in the client config. On first connection, you will be guided through Spotify authorization with no API keys or local setup needed.

Key features of Spotify

• 80 tools covering the complete Spotify Web API
• Remote MCP via Streamable HTTP transport
• OAuth2 proxy with PKCE and dynamic client registration
• Automatic token refresh with encrypted storage (AES-256-GCM)
• Supabase backend for tokens, sessions, and clients
• Tool analytics with 90‑day retention and scheduled cleanup
• Landing page with live health status

Use cases of Spotify

• Control Spotify playback (play, pause, skip, seek, queue) from an AI chat
• Manage playlists: create, modify, add or remove items, and change cover images
• Search across all Spotify content types with field filters
• Save, remove, and check saved albums, tracks, episodes, shows, and audiobooks
• Follow or unfollow artists and users, and view top items

FAQ from Spotify

How does the OAuth authorization work?

The server acts as an OAuth2 proxy between MCP clients and Spotify. After you connect, you are redirected to Spotify to authorize, and the server exchanges the authorization code for tokens. Tokens are automatically refreshed and encrypted at rest.

What runtime or dependencies are needed to run my own instance?

You need Bun v1.3+, a Spotify Developer App (client ID and secret), and a Supabase project. The server can be deployed using the included Dockerfile.

Where are user tokens and data stored?

Tokens are stored in a Supabase database, encrypted at rest with AES-256-GCM. Anonymous tool analytics are retained for 90 days, after which expired tokens, sessions, and analytics are automatically purged.

What transport protocol does the server use?

The server uses Streamable HTTP transport for remote MCP communication. It also provides a landing page, health check endpoint, and OAuth server metadata endpoint.

What tools are available?

80 tools covering 13 categories: Albums, Artists, Audiobooks, Chapters, Episodes, Library (unified), Markets, Player (15 tools), Playlists, Search, Shows, Tracks, and Users. All save/remove/check library operations use the new unified Spotify /me/library endpoint with Spotify URIs.