{"version":"2.1.299","anchor":"subagent-mcp-servers-need-project-approval","canonical_anchor":"subagent-mcp-servers-need-project-approval","heading":"Subagents can only use MCP servers approved for the project","tier":"notice","area":"Subagents","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/subagent-mcp-servers-need-project-approval","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Subagents can only use MCP servers approved for the project\n\nMCP servers a subagent asks for are skipped unless approved for the project, with a note to approve them through `\/mcp`\n\n**What**\n\nA subagent is a helper agent that Claude Code starts for a task, and its definition can list MCP servers (add-ons that give extra tools). Those servers are now skipped if they have not been approved for the current project. Claude Code reports them as \"missing project approval (approve via \/mcp)\". Before, only servers blocked by a managed policy were kept out.\n\n**Why**\n\nAn agent defined in a project you have not approved can no longer quietly connect its own MCP servers. To use them, approve them with `\/mcp`.\n\n- Area: Subagents\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}