{"version":"2.1.310","anchor":"mcp-server-status-new-switched-off-state-for-connected-se","canonical_anchor":"mcp-server-status-new-switched-off-state-for-connected-se","heading":"Connected MCP servers can now report a \"switched_off\" sign-in status","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/mcp-server-status-new-switched-off-state-for-connected-se","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Connected MCP servers can now report a \"switched_off\" sign-in status\n\nA connected or cached MCP server can now report its sign-in status as switched_off before any other result\n\n**Unclear.** It is not stated what makes a connected server count as switched off.\n\n**What**\n\nThe `switched_off` status now reaches more MCP servers (outside programs that give Claude Code extra tools). When Claude Code works out the sign-in status of a server that is connected, or that it has a saved connection for, it now first checks whether the server is switched off and, if so, reports `switched_off`. Previously such servers went straight to a status saying sign-in was completed or was not offered.\n\n**Why**\n\nIf you read MCP server status, for example from a program built on the SDK, a connected server can now come back as `switched_off`. Code that only expects the sign-in results may not handle it.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}