{"version":"2.1.295","anchor":"mcp-server-status-switched-off-treated-as-a-terminal-state","canonical_anchor":"mcp-server-status-switched-off-treated-as-a-terminal-state","heading":"MCP servers can now be reported as switched off","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-server-status-switched-off-treated-as-a-terminal-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### MCP servers can now be reported as switched off\n\nA new `switched_off` status for MCP servers, now used for SDK servers, tells Claude a server was switched off rather than disabled by you\n\n**Unclear.** How an MCP server comes to be marked switched_off is not known.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. A new server status, `switched_off`, has been added:\n\n- It joins the group of states where a server is unavailable, alongside `org_blocked`, `denied`, `disabled` and `not_configured`.\n\n- A disabled MCP server of type `sdk` (one created through the SDK, the toolkit for driving Claude Code from code) now reports `switched_off` instead of `disabled`.\n\n- When Claude tries a tool from such a server, it is told the server `has been switched off. Continue without this tool.` This is separate from the existing `disabled` message, which says the user disabled the server.\n\n**Why**\n\nClaude gets a more accurate reason when a server goes away mid-session. If you use the SDK and check server status, expect `switched_off` where you used to see `disabled`.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}