[BUG] Stale MCP OAuth client_id
Resolved 💬 3 comments Opened Jul 30, 2025 by Adamovskiy Closed Aug 4, 2025
- Connect Claude Desktop to a remote MCP using OAuth. A client is created dynamically.
- The previously created client is removed on the MCP side.
- 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 anerrorquery parameter nor the "Reload MCP configuration" menu item resets cached client_id.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗