Unclear What these changes mean in practice for someone using MCP servers is not clear.
MCP servers are add-ons that give Claude extra tools through the Model Context Protocol. Claude Code now works out which of them need sign-in through a new step, instead of listing them directly. It also changes how it decides that a server should be reconnected on the next turn.
The setting for the newer MCP connection handshake over claude.ai connections now falls back to on when the server sends nothing. The flag server was returning it on for this site's account and for a signed-out account, a change since the previous reading.
This changes how MCP servers that need sign-in, and their reconnects, are reported to the model.
tengu_mcp_protocol_negotiation_claudeai On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.295: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.295. It isn't a statement about your account. What a flag value here can and cannot tell you
What these changes mean in practice for someone using MCP servers is not clear.