7IT Solutions
7MapsOverviewLive chartStateReliableMethodologyVerifyFor agentsFor ownersNews

Your MCP token expired. Claude Code ended the call with TOKEN_EXPIRED until 2.1.323.

By Lior AharonovFounder, 7IT Solutions ·

What happened

Claude Code 2.1.323 shipped on Thursday, 12 November 2026. One fix: MCP tool calls used to end in the sign-in server's own error, such as TOKEN_EXPIRED, instead of asking the user to sign in again. The same release adds an engines["claude-code"] field to plugin.json, so a plugin outside its stated version range is not installed, updated or loaded.

Why it matters

Picture the user mid-afternoon: the morning token lapses, the sign-in server answers TOKEN_EXPIRED, and the chat just stops. To them, your server looks broken. Now they get a sign-in prompt instead.

What to do

Upgrade Claude Code to 2.1.323, let a test token expire, and confirm your MCP tool call ends in a sign-in prompt. If you ship a plugin, add engines["claude-code"] to plugin.json with the version range you tested.

My take

Lior Aharonov
Founder, 7IT Solutions

An expired token is not an outage. It just looked like one in the chat.

Sources

Claude Code 2.1.323 changelograw.githubusercontent.com
@anthropic-ai/claude-code 2.1.323 on npmregistry.npmjs.org
mcpclaude-codeoauthplugins

Researched with AI tools; every fact is checked against the linked sources.

7Maps news

Every 7Maps day is signed and chained to the day before.Verify in your browser