{"version":"2.1.286","anchor":"mcp-needs-auth-state-handling-fixed","canonical_anchor":"mcp-needs-auth-state-handling-fixed","heading":"Fixed how MCP servers are marked as needing sign-in","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/mcp-needs-auth-state-handling-fixed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Fixed how MCP servers are marked as needing sign-in\n\nClaude Code now handles marking an MCP server as needing authentication correctly, where before it returned the wrong value\n\n**What**\n\nMCP servers are outside tools that Claude Code connects to. Some of them need you to sign in first, and Claude Code then marks the connection as `needs-auth`. The code that sets this mark returned the wrong value and read a value that was never set. It now works as follows:\n\n- When the server is missing, or is neither connected nor already marked `needs-auth`, the stored state stays as it was.\n\n- When the server is already marked `needs-auth`, that entry stays as it is.\n\n**Why**\n\nThis fixes a bug in how Claude Code keeps track of which MCP servers still need you to sign in.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}