{"version":"2.1.268","anchor":"mcp-needs-auth-servers-are-now-tracked-and-surfaced-once-p","canonical_anchor":"mcp-needs-auth-servers-are-now-tracked-and-surfaced-once-p","heading":"MCP 'needs auth' servers are now tracked and surfaced once per session\/persistently","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-needs-auth-servers-are-now-tracked-and-surfaced-once-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCP 'needs auth' servers are now tracked and surfaced once per session\/persistently\n\nClaude Code now avoids repeatedly nagging you about the same MCP server needing authentication\n\n**What**\n\nWhen an MCP server (a connected external tool server) needs authentication, Claude Code now keeps track of which servers it has already flagged to you, both for the current session and persisted across sessions (with a cap on how many are remembered). Once a server successfully connects, it is cleared from that list.\n\n**Why**\n\nThis stops the same 'needs auth' notice from being shown over and over for a server you already know about, while still re-flagging it if it later needs attention again.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}