[FEATURE] Claude Desktop should offer to re-auth with MCP if auth has expired

Open 💬 2 comments Opened Jun 25, 2026 by jc0b

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

MCP servers using OAuth sometimes have their tokens expire. When this happens, employees need to click "Disconnect" and "Reconnect" in the MCP server settings to get their auth back.

Proposed Solution

This feature request covers to things:

  1. There should be a simple "reconnect" button available for each MCP server
  2. If using a tool in a chat, and the MCP server returns that the token is invalid or otherwise expired, Claude should present an option to reconnect right there in the transcript.

This would reduce friction significantly for employees using OAuth-authenticated MCPs where the tokens may not be valid indefinitely.

Alternative Solutions

At the moment, we are instructing employees to disconnect and connect again.

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

Example scenario:

  1. I am working with an MCP server one day, using tools
  2. The next day (or some days after), I try use tools again
  3. Claude tells me it can't use the tools due to an authorization issue, but offers that it can attempt to reconnect right there in the transcript
  4. I click reconnect
  5. I re-do OAuth
  6. I continue on with my tool use, without having to leave the context of the chat I'm in.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗