[GH-ISSUE #18] Update Spotify redirect URI to comply with new requirements - localhost deprecated #8

Closed
opened 2026-02-28 15:42:48 +03:00 by kerem · 0 comments
Owner

Originally created by @hyuma7 on GitHub (Apr 13, 2025).
Original GitHub issue: https://github.com/varunneal/spotify-mcp/issues/18

Image

https://developer.spotify.com/documentation/web-api/concepts/redirect_uri

Problem

Spotify is enforcing new redirect URI validation rules starting April 9, 2025, with all clients required to migrate by November 2025. This change means our current configuration using http://localhost:8888 will no longer work.

Changes from Spotify

According to Spotify's new requirements:

  • When using a loopback address, explicit IPv4/IPv6 addresses must be used instead of localhost
  • Allowed redirect URI examples: http://127.0.0.1:8888/callback or http://[::1]:8888/callback

Required Actions

  1. Update documentation to instruct users to set the redirect URI to http://127.0.0.1:8888 (or their preferred port)
  2. Update any code references to the redirect URI
  3. Update configuration examples in the README

Impact

This breaking change affects all users who create new Spotify apps after April 9, 2025, and will affect all existing apps by November 2025.

Priority

Medium: Required by November 2025, but already affecting new app creation.

This change is essential for continued use of the Spotify API. More details can be found on the Spotify Developer Blog.

Originally created by @hyuma7 on GitHub (Apr 13, 2025). Original GitHub issue: https://github.com/varunneal/spotify-mcp/issues/18 ![Image](https://github.com/user-attachments/assets/827e4f4d-ada6-4438-8494-093c2d935826) https://developer.spotify.com/documentation/web-api/concepts/redirect_uri ### Problem Spotify is enforcing new redirect URI validation rules starting April 9, 2025, with all clients required to migrate by November 2025. This change means our current configuration using `http://localhost:8888` will no longer work. ### Changes from Spotify According to Spotify's new requirements: - When using a loopback address, explicit IPv4/IPv6 addresses must be used instead of `localhost` - Allowed redirect URI examples: `http://127.0.0.1:8888/callback` or `http://[::1]:8888/callback` ### Required Actions 1. Update documentation to instruct users to set the redirect URI to `http://127.0.0.1:8888` (or their preferred port) 2. Update any code references to the redirect URI 3. Update configuration examples in the README ### Impact This breaking change affects all users who create new Spotify apps after April 9, 2025, and will affect all existing apps by November 2025. ### Priority Medium: Required by November 2025, but already affecting new app creation. This change is essential for continued use of the Spotify API. More details can be found on the Spotify Developer Blog.
kerem closed this issue 2026-02-28 15:42:48 +03:00
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-mcp-varunneal#8
No description provided.