{"version":"2.1.295","anchor":"mcp-needs-auth-redial-gating-changes","canonical_anchor":"mcp-needs-auth-redial-gating-changes","heading":"Changes to how MCP servers needing sign-in are reported","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-needs-auth-redial-gating-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Changes to how MCP servers needing sign-in are reported\n\nClaude Code changes how it lists MCP servers that need sign-in and when it reconnects them on the next turn\n\n**Unclear.** What these changes mean in practice for someone using MCP servers is not clear.\n\n**What**\n\nMCP 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.\n\nThe 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.\n\n**Why**\n\nThis changes how MCP servers that need sign-in, and their reconnects, are reported to the model.\n\n- Flag `tengu_mcp_protocol_negotiation_claudeai`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.295; this account: on, anonymous baseline: on, compiled default: 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.\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}