{"version":"2.1.295","anchor":"mcp-switched-off-denial-reason-and-next-turn-redial","canonical_anchor":"mcp-switched-off-denial-reason-and-next-turn-redial","heading":"New \"MCP server switched off\" reason for blocked MCP tools","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-switched-off-denial-reason-and-next-turn-redial","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### New \"MCP server switched off\" reason for blocked MCP tools\n\nClaude Code has a new reason, \"MCP server switched off\", for blocking an MCP tool, and now tracks reconnecting a server on the next turn\n\n**Unclear.** It is not stated how a server gets switched off, or whether you can do it yourself.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools, connected through the Model Context Protocol. Claude Code now has a new reason it can give when it blocks one of those tools: \"MCP server switched off\".\n\nClaude Code also records a new internal measurement for reconnecting to an MCP server on the next turn. A turn is one exchange between you and Claude.\n\n**Why**\n\nThe new reason points to MCP servers that can be switched off, and to Claude Code trying to reconnect to a server on the following turn.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}