claude-code - 💡(How to fix) Fix Feature Request: Automatic MCP reconnection on auth token expiry [1 comments, 2 participants]

TL;DR

Implement automatic reconnect logic in Claude Code to re-execute headersHelper and retry failed requests when encountering 401/403 errors from the HTTP MCP server.

Guidance

• Identify the specific error handling mechanism in Claude Code that catches 401/403 errors from the HTTP MCP server and modify it to trigger a reconnect.
• Re-executing headersHelper should obtain a fresh auth token, which can then be used to retry the original failed request.
• Consider implementing a retry limit to prevent infinite loops in case of persistent authentication issues.
• Verify that the reconnect logic correctly handles different scenarios, such as multiple concurrent requests failing due to token expiration.

Example

// Pseudo-code example of reconnect logic
if (response.status === 401 || response.status === 403) {
  const freshToken = await reExecuteHeadersHelper();
  // Retry the original request with the new token
  return retryRequestWithToken(freshToken);
}

Notes

The exact implementation details may vary depending on the specific architecture and technology stack used by Claude Code. This guidance assumes that headersHelper can be re-executed programmatically to obtain a fresh auth token.

Recommendation

Apply workaround: Implement the reconnect logic as described, as there is no indication of a fixed version that addresses this issue. This approach allows for a more robust handling of short-lived auth tokens without relying on manual user intervention or external workarounds.