{"version":"2.1.283","anchor":"subagent-mcp-servers-skipped-when-their-name-is-reserved-by","canonical_anchor":"subagent-mcp-servers-skipped-when-their-name-is-reserved-by","heading":"Subagent MCP servers are skipped when the session already uses that name","tier":"notice","area":"Subagents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/subagent-mcp-servers-skipped-when-their-name-is-reserved-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Subagent MCP servers are skipped when the session already uses that name\n\nClaude Code now skips connecting a subagent's MCP server if the session is holding that server name for its own use\n\n**Unclear.** It is not clear which server names count as held by the session.\n\n**What**\n\nA subagent is a helper that Claude starts to work on part of a task. A subagent can define its own MCP servers, which are programs that give Claude extra tools.\n\nBefore connecting one of those servers, Claude Code now checks whether the session is holding that server name for its own entry. If it is, the subagent's server is skipped with the message \"skipped: the session holds this server name for its own entry\". The name counts as held in either of two cases:\n\n- a condition set by the session applies\n\n- the session has already set up its own memory tools entry\n\nBefore, the only check was against the administrator's managed-settings rules for MCP servers.\n\n**Why**\n\nThis stops a subagent's server from replacing a server the session relies on under the same name.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}