Issue Configuring MCP OAuth for Spotify — Getting “Missing or invalid access token” Error

[ABHIJITH-EA]

What happened?

I'm trying to set up the Spotify MCP using OAuth with the streamable-http type in LibreChat. I followed the documentation and created a Spotify Developer App. I configured the librechat.yaml like this:

mcpServers:
  spotify:
    type: "streamable-http"
    url: "https://spotify-mcp.localhost/mcp"
    env:
      SPOTIFY_CLIENT_ID: "my-client-id"
      SPOTIFY_CLIENT_SECRET: "my-client-secret"

I expected it to initiate the OAuth flow or at least provide a link to authenticate, but it seems like it's skipping that and server initialization is failed.

Additional Info:

• I'm running the MCP server locally at https://spotify-mcp.localhost/mcp with a self-signed certificate (already trusted in the system and added NODE_TLS_REJECT_UNAUTHORIZED=0 in .env of librechat).
• I didn't find additional configuration details in the docs beyond setting the CLIENT_ID and CLIENT_SECRET.

Version Information

bef5c26

Steps to Reproduce

1. clone the MCP server https://github.com/LibreChat-AI/spotify-mcp
2. npm install
3. npm run dev
4. connect librechat to the mcp server by configuring librechat.yaml

What browsers are you seeing the problem on?

No response

Relevant log output

2025-07-25T08:44:56.374Z info: OpenID Connect configured.
2025-07-25T08:44:56.380Z info: Server listening at http://localhost:3080
2025-07-25T08:44:56.380Z info: Initializing MCP servers...
2025-07-25T08:44:56.631Z debug: [mcp_get_tokens:tokens:000000000000000000000000:spotify] Creating initial flow state
2025-07-25T08:44:56.637Z info: [MCP][spotify] Access token missing
2025-07-25T08:44:56.640Z info: [MCP][spotify] Access token missing and no refresh token available
2025-07-25T08:44:56.665Z info: [MCP][spotify] Setting up OAuth event listener
2025-07-25T08:44:56.665Z info: [MCP][spotify] Creating streamable-http transport: https://spotify-mcp.localhost/mcp
2025-07-25T08:44:56.666Z debug: [MCP][spotify] Transport sending: {"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"@librechat/a... [truncated]
2025-07-25T08:44:56.681Z error: [MCP][spotify] Transport error: Error POSTing to endpoint (HTTP 401): Missing or invalid access token
2025-07-25T08:44:56.682Z info: [MCP][spotify] Streamable-http transport closed
2025-07-25T08:44:56.682Z warn: [MCP][spotify] OAuth authentication required
2025-07-25T08:44:56.682Z debug: [MCP][spotify] Server URL for OAuth: https://spotify-mcp.localhost/mcp
2025-07-25T08:44:56.682Z debug: [MCP][spotify] oauthRequired event received
2025-07-25T08:44:56.682Z info: [MCP][spotify] OAuth required, skipping at startup
2025-07-25T08:44:56.683Z error: [MCP][spotify] OAuth handling failed: OAuth authentication skipped at startup
2025-07-25T08:44:56.683Z error: [MCP][spotify] Connection failed: Error POSTing to endpoint (HTTP 401): Missing or invalid access token
2025-07-25T08:44:56.683Z info: [MCP][spotify] OAuth required, stopping connection attempts
2025-07-25T08:44:56.683Z error: [MCP][spotify] Initialization failed Error POSTing to endpoint (HTTP 401): Missing or invalid access token
2025-07-25T08:44:56.683Z error: [MCP][spotify] Initialization failed Error POSTing to endpoint (HTTP 401): Missing or invalid access token
2025-07-25T08:44:56.683Z info: [MCP] Initialized 0/1 app-level server(s)
2025-07-25T08:44:56.684Z info: [MCP][spotify] ✗ Failed
2025-07-25T08:44:56.684Z warn: [MCP] No app-level servers initialized
2025-07-25T08:44:56.685Z debug: Cleared tools array cache after MCP initialization
2025-07-25T08:44:56.685Z info: MCP servers initialized successfully

Screenshots

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

You're missing a step for the MCP server setup.

Make sure to do Step #2 to fill .dev.vars.

https://github.com/LibreChat-AI/spotify-mcp/tree/main?tab=readme-ov-file#2-configure-environment-variables

[ABHIJITH-EA]

@danny-avila Hi,
Thanks for your response.
I’ve already completed step 2 and filled in the .dev.vars file, but I'm still encountering the same error.