Claude Code Now Asks You to Confirm MCP Server Sign-Ins, Even in Bypass and Auto Modes
Claude CodeView original changelog
Claude Code 2.1.323 changes the tool Claude uses to finish an MCP server sign-in so that it asks the user to confirm, even in bypass and auto modes. Where nobody can be asked, such as dontAsk mode, users must sign in through /mcp.
Key Takeaways
- MCP sign-in completion now needs confirmation, even in bypass and auto modes.
- In
dontAskmode, users sign in through/mcpinstead. - Expired tokens like
TOKEN_EXPIREDnow prompt a fresh sign-in rather than surfacing a raw error. - Project
.mcp.jsonapprovals now require the server's exact name. - Sign-in is now treated as a step that always needs a person, unlike other bypassable prompts.
- It shipped in Claude Code 2.1.323.
What changed
The tool Claude uses to complete an MCP server sign-in now asks the user to confirm in Claude Code 2.1.323. This applies even in bypass and auto modes, which normally skip prompts. Where nobody can be asked, such as in dontAsk mode, the sign-in must be done with /mcp.
Related MCP fixes
MCP tool calls that ended in the sign-in server's error, such as TOKEN_EXPIRED, now lead to a request to sign in again. Project (.mcp.json) MCP server approvals now match the server's exact name, so an approval written in another spelling asks again.