mcp-spotify-render

The server utilizes OAuth 2.0 for Spotify authentication, requiring users to configure `clientId`, `clientSecret`, and a `redirectUri` in a `spotify-config.json` file. The authentication flow involves a temporary local HTTP server (`127.0.0.1`) for exchanging authorization codes for tokens, which are then saved locally. No hardcoded secrets are found. The primary Node.js server does not directly expose any network listeners other than the temporary one for OAuth. Both implementations (Node.js and an alternative Python server for multi-tenant HTTP deployments) use standard, well-maintained libraries for API interaction. No `eval` or code obfuscation is present.