[BUG] v2.1.177 update invalidated OAuth tokens for all claude.ai remote MCPs

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

After updating to 2.1.177, all claude.ai remote MCP connections lost their OAuth tokens and are no longer available in sessions.

Before update: 16 remote MCPs were active (Microsoft 365, Slack, Gmail, Notion, ChEMBL, Clinical Trials, NPI Registry, Excalidraw, etc.), confirmed via claudeAiMcpEverConnected in ~/.claude.json.

After update: 22 remote MCPs appear in ~/.claude/mcp-needs-auth-cache.json as needing re-authentication. Microsoft 365 is not even in the needs-auth queue — it is completely absent from the session.

Local MCPs (defined in mcpServers in ~/.claude.json) are unaffected.

Expected: Update should preserve existing OAuth tokens for remote claude.ai MCPs.
Actual: All remote MCP tokens invalidated; users must re-authenticate every connector.

The /mcp dialog does not appear to offer a clear re-authentication flow for the affected servers.

What Should Happen?

Claude code should pick up the MCP configurations and port them to the new version.

Error Messages/Logs

Steps to Reproduce

brew update claude-code

/mcp

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.177

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_