A brief token refusal left MCP servers stuck on sign-in. Claude Code 2.1.325 fixes it.
By Lior AharonovFounder, 7IT Solutions ·
What happened
Claude Code 2.1.325 shipped on Friday, 13 November 2026. Its changelog says an MCP server could stay at "needs authentication", and its mcp_tool hooks be skipped, after a token refresh was refused only for a moment. The same release fixes headless elicitation requests cancelled without asking, and SDK host tool calls answering "Not connected" after a reconnect.
Why it matters
Your server did nothing wrong. Yet the user saw a sign-in wall and the hooks went quiet. A hiccup of one moment could read as your outage.
What to do
If users reported sign-in loops or "Not connected" errors with your MCP server, ask them to update to Claude Code 2.1.325 before you debug your own token code.

My take
Lior Aharonov
Founder, 7IT Solutions
A token refresh that fails for a moment should heal in a moment. Until this release, it didn't.
Sources
| Claude Code 2.1.325 changelog | raw.githubusercontent.com |
| @anthropic-ai/claude-code 2.1.325 on npm | registry.npmjs.org |
Researched with AI tools; every fact is checked against the linked sources.