{"version":"2.1.239","anchor":"more-specific-explanations-when-an-mcp-config-is-ignored","canonical_anchor":"more-specific-explanations-when-an-mcp-config-is-ignored","heading":"More specific explanations when an --mcp-config is ignored","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/more-specific-explanations-when-an-mcp-config-is-ignored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### More specific explanations when an --mcp-config is ignored\n\nSkipped --mcp-config servers now name managed settings or a Remote Control child as the reason.\n\n**What**\n\nTwo new reasons now appear when servers passed on the command line are skipped: a managed setting on the machine forbids server-delivered MCP servers, and the session is a Remote Control child. A table of bridge rejection reasons was added alongside them.\n\n**Details**\n\n- The managed setting named in the message is `disableSideloadFlags`.\n- Bridge rejection reasons cover a foreign entry, a non-http type, a URL mismatch, a missing ingress origin and a missing session id.\n\n**Evidence**\n\n`Ignored: managed setting disableSideloadFlags forbids server-delivered MCP servers on this machine`\n\n- Area: MCP\n- Names: `--mcp-config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}