Spotify MCP

Search music, manage playlists, and control Spotify playback from your AI assistant.

  1. Sign in and connect Spotify

    Sign in to the account page with an allowed email, choose whether to allow playback and library/playlist changes, then select Connect or reconnect Spotify. Approve the permissions on Spotify’s own consent screen and return to the account page. You do not enter your Spotify password or create a Spotify API token here.

    This hosted server uses the operator’s Spotify application. If that app is in Spotify Development Mode, Spotify requires the app owner to have Premium and limits the app to five allowlisted users; an invitation to this MCP account alone does not grant Spotify app access. If Spotify returns an access error, ask the operator whether the app is in Development Mode and whether your Spotify account is allowlisted. Spotify playback control also requires Premium and a Spotify Connect device with playback active.

    To disconnect or replace your Spotify authorization, use the account page. You can revoke the app from Spotify account settings as well.

  2. Create a personal MCP token or use OAuth

    For bearer-token clients, open Access tokens, create a named token with only the read/write capability you need, set an expiry, and copy it once. It is separate from Spotify authorization. Revoke it from the same page if exposed.

    OAuth-capable MCP clients may instead add the server URL and sign in through OAuth discovery. Review the client’s requested access and approve only a client you recognize. OAuth grants read-only access; use a personal token if you need the explicit write permissions offered by this service.

  3. Configure your MCP client

    Use remote Streamable HTTP at:

    https://spotify-mcp.sherwoodcallaway.com/mcp

    Claude Code bearer-token example:

    claude mcp add --transport http spotify https://spotify-mcp.sherwoodcallaway.com/mcp --header "Authorization: Bearer <YOUR_PERSONAL_MCP_TOKEN>"

    Other Streamable HTTP clients can use the URL and Authorization: Bearer <YOUR_PERSONAL_MCP_TOKEN> header. OAuth clients should use their built-in OAuth flow instead of adding a bearer token. MCP Gateway is optional.

  4. Verify and manage access

    Reload the tools and call search for account_status, then execute it. Confirm the returned Spotify profile is yours; try a read-only operation before enabling writes.

    • 401 Unauthorized: check that your MCP token is current and the Authorization header is exactly Bearer <token>; mint a replacement if revoked or expired.
    • Spotify 403: confirm your Spotify account was added to the app’s allowlist and the app has quota eligibility.
    • Playback unavailable: Spotify Premium is required; open Spotify on a Connect device and start playback.
    • 429: pause and retry later; development-mode apps share the developer account’s quota.

    Disconnect Spotify and revoke MCP tokens from the account page when you want to remove this server’s access.