{"version":"2.1.269","anchor":"eval-mocks-plugins-with-unenumerable-mcp-servers-now-handle","canonical_anchor":"eval-mocks-plugins-with-unenumerable-mcp-servers-now-handle","heading":"Eval mocks: plugins with unenumerable MCP servers now handled explicitly","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/eval-mocks-plugins-with-unenumerable-mcp-servers-now-handle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Eval mocks: plugins with unenumerable MCP servers now handled explicitly\n\nEval mocking now gives specific errors when a plugin's MCP servers can't be enumerated for mocking\n\n**What**\n\nThe eval mocking system can now detect and explain three specific cases where a plugin's MCP servers can't be listed for mocking:\n\n- the plugin is a packaged archive\n\n- the plugin's manifest fails to load\n\n- the plugin declares its servers through an MCPB bundle\n\nInstead of failing with a generic error, record mode now tells the operator exactly what to do: extract the archive, fix the manifest, or pass `--allow-real-servers`.\n\n**Why**\n\nThis turns a previously generic failure into an actionable message, so someone recording an eval knows exactly what's blocking it and how to resolve it.\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}