{"version":"2.1.323","anchor":"mcp-detach-message-depends-on-a-check","canonical_anchor":"mcp-detach-message-depends-on-a-check","heading":"The note about a detached MCP server now comes in two forms","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-detach-message-depends-on-a-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### The note about a detached MCP server now comes in two forms\n\nWhen an MCP server is detached, the model now gets one of two notes: avoid all of its tools, or a note naming one tool\n\n**What**\n\nAn MCP server is a connection that gives Claude Code extra tools. When one is detached, Claude Code tells the model about it. That message now has two forms, and a check picks which one is used:\n\n- One tells the model not to call that server's tools until it is attached again.\n\n- The other names a specific tool.\n\n**Why**\n\nThe message tells the model how to treat the tools of a server that is no longer attached.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}