{"version":"2.1.323","anchor":"mcp-connection-start-is-gated-by-a-per-server-ask-before-dia","canonical_anchor":"mcp-connection-start-is-gated-by-a-per-server-ask-before-dia","heading":"MCP servers go through an extra check before connecting","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-connection-start-is-gated-by-a-per-server-ask-before-dia","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### MCP servers go through an extra check before connecting\n\nBefore connecting to each MCP server, Claude Code now runs an extra step that can skip that server\n\n**Unclear.** It is not stated what the new check looks at or when it skips a server.\n\n**What**\n\nMCP servers are outside services Claude Code connects to for extra tools. Before connecting to each one, Claude Code now runs an extra check step that can skip the server. The usual checks, such as whether Claude Code is shutting down, whether the server is turned off, or whether it is blocked by managed policy, now run both before and after this step.\n\n**Why**\n\nThis adds a point where an MCP server can be held back before Claude Code connects to it.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}