{"version":"2.1.304","anchor":"subagent-frontmatter-mcp-servers-are-blocked-in-cloud-sessio","canonical_anchor":"subagent-frontmatter-mcp-servers-are-blocked-in-cloud-sessio","heading":"Subagents' own MCP servers are skipped in cloud sessions","tier":"notice","area":"Subagents","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/subagent-frontmatter-mcp-servers-are-blocked-in-cloud-sessio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Subagents' own MCP servers are skipped in cloud sessions\n\nIn a cloud session, MCP servers listed in a subagent's own definition are no longer started\n\n**What**\n\nA subagent is a helper Claude Code starts to handle part of a task. Its definition file can list its own MCP servers. MCP (Model Context Protocol) is the way Claude Code connects to outside tools. In a cloud session, Claude Code now skips those servers and gives \"this cloud session\" as the reason.\n\n**Why**\n\nSubagents in cloud sessions lose access to MCP servers listed in their own definition. Tools that depend on those servers will not be available there.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}