{"version":"2.1.311","anchor":"mcp-servers-switched-off-are-recorded-in-worker-metadata-and","canonical_anchor":"mcp-servers-switched-off-are-recorded-in-worker-metadata-and","heading":"MCP servers you switch off stay off when a remote session is resumed","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/mcp-servers-switched-off-are-recorded-in-worker-metadata-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### MCP servers you switch off stay off when a remote session is resumed\n\nClaude Code now saves which MCP servers you switched off in a session and switches them off again when a remote worker resumes it\n\n**Unclear.** It is not known what condition decides whether this saving and restoring happens for you.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. When you switch one off, Claude Code now saves the list of switched-off servers with the session's internal details. When a remote worker (a copy of Claude Code running the session on another machine) resumes the session, it switches those servers off again. Before, this list was not saved.\n\n**Why**\n\nServers you turned off stay off after a resume instead of coming back on.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}