{"version":"2.1.267","anchor":"sub-agent-tool-resolution-now-includes-machine-level-mcp-too","canonical_anchor":"sub-agent-tool-resolution-now-includes-machine-level-mcp-too","heading":"Sub-agent tool resolution now includes machine-level MCP tools","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/sub-agent-tool-resolution-now-includes-machine-level-mcp-too","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Sub-agent tool resolution now includes machine-level MCP tools\n\nSpawned subagents can now use machine-level MCP tools, not just app-state and agent-declared ones\n\n**What**\n\nWhen Claude Code figures out which tools a spawned subagent is allowed to use, it now also includes machine-level MCP (Model Context Protocol, a standard for connecting external tools) tools, in addition to the app-state MCP tools and the tools an agent explicitly declares. This applies both to subagent spawning generally and to the workflow SDK's agent tool-set resolution, and the machine-level tool list is now merged in when building skill tool sets as well.\n\n**Why**\n\nThis broadens what tools a subagent can reach, so machine-wide MCP tool configurations are no longer left out when a subagent's tool set is computed.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}