1. Connect Claude Desktop to a remote MCP using OAuth. A client is created dynamically. 2. The previously created client is removed on the MCP side. 3. Subsequent attempts to connect to the same MCP display the authorization endpoint's browser page with the same old `client_id`. There is no clear way to inform the client that the ID has expired: neither a callback URL with an `error` query parameter nor the "Reload MCP configuration" menu item resets cached client_id.

[BUG] Stale MCP OAuth client_id

Status Fixed / completed

Maintainer reply None cached

Activity 3 comments · opened Jul 30, 2025 · closed Aug 4, 2025

Connect Claude Desktop to a remote MCP using OAuth. A client is created dynamically.

Subsequent attempts to connect to the same MCP display the authorization endpoint's browser page with the same old client_id. There is no clear way to inform the client that the ID has expired: neither a callback URL with an error query parameter nor the "Reload MCP configuration" menu item resets cached client_id.