{"version":"2.1.319","anchor":"subagent-mcp-servers-get-a-bound-dial-check-before-connectin","canonical_anchor":"subagent-mcp-servers-get-a-bound-dial-check-before-connectin","heading":"Subagents may skip some MCP servers that fail a connection check","tier":"notice","area":"Subagents","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/subagent-mcp-servers-get-a-bound-dial-check-before-connectin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Subagents may skip some MCP servers that fail a connection check\n\nBefore a subagent connects to certain MCP servers, Claude Code now runs a check and skips the server with a warning if it fails\n\n**Unclear.** Which kinds of MCP server get this check is not settled.\n\n**What**\n\nBefore a subagent (a helper copy of Claude given part of a task) connects to certain kinds of MCP server, Claude Code now runs a connection check first. MCP servers are outside tools Claude can use. If the check fails, the server is skipped and a warning says which server was skipped.\n\n**Why**\n\nThis is a new reason an MCP server may be unavailable inside a subagent, so a skipped-server warning is worth looking for if a tool is missing there.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}