{"version":"2.1.269","anchor":"eval-mock-harness-managed-mcpjson-now-takes-exclusive-mcp","canonical_anchor":"eval-mock-harness-managed-mcpjson-now-takes-exclusive-mcp","heading":"Eval-mock harness: managed-mcp.json now takes exclusive MCP control","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/eval-mock-harness-managed-mcpjson-now-takes-exclusive-mcp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Eval-mock harness: managed-mcp.json now takes exclusive MCP control\n\nEval\/mock testing tool's managed-mcp.json config now fully overrides other mock MCP servers, erroring if a required one is skipped\n\n**What**\n\nThis is a change to Claude Code's internal evaluation and mock-testing tooling, not something end users interact with directly. When a `managed-mcp.json` configuration file and a new mode are both active, any stand-in (mocked) MCP servers marked as withheld are no longer registered in the test process. If a mocked server that is actually required (not withheld) would still need registering, a new dedicated error is thrown instead of letting it proceed.\n\nThis builds on an existing behavior where an enterprise-managed `managed-mcp.json` file, when present in remote mode, drops MCP servers from other sources.\n\n**Why**\n\nThis tightens internal test tooling so a `managed-mcp.json` config behaves consistently and fails loudly, rather than silently, when a required mock server is missing.\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}