{"version":"2.0.56","anchor":"command-based-mcp-server-matching","canonical_anchor":"command-based-mcp-server-matching","heading":"Command-Based MCP Server Matching","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.56\/e\/command-based-mcp-server-matching","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.56","markdown":"### Command-Based MCP Server Matching\n\n**What:** Enterprise admins can now allow or deny MCP servers by their exact command invocation, not just by name.\n\n**How to use:**\n\n`{ \"allowedMcpServers\": [ { \"serverName\": \"weather\" }, { \"serverCommand\": [\"npx\", \"-y\", \"@company\/approved-server\"] } ] }` **Details:**\n\n- Each entry must have EITHER `serverName` OR `serverCommand`, not both\n- Command matching requires exact array equality (all arguments must match)\n- Backward compatible - name-based matching still works\n- New functions `TzA()` at line 509000 and `KiA()` at line 509003 for type checking\n- **Evidence**: `O8B()` at line 185472, `Tv1()` at line 185485, schema at line 509164-509190"}