{"version":"2.1.239","anchor":"remote-control-bridge-sessions-reject-foreign-mcp-config-ent","canonical_anchor":"remote-control-bridge-sessions-reject-foreign-mcp-config-ent","heading":"Remote Control bridge sessions reject foreign --mcp-config entries","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/remote-control-bridge-sessions-reject-foreign-mcp-config-ent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Remote Control bridge sessions reject foreign --mcp-config entries\n\nRemote Control bridge children reject foreign --mcp-config servers and rebuild the meta server themselves.\n\n**What**\n\nA session running as a Remote Control bridge child now drops dynamically supplied MCP servers unless the entry is the Remote Control meta server, and rebuilds even that one from the approved startup address and session id instead of trusting the file. There is no flag: this applies whenever the process is a bridge carrier child.\n\n**Details**\n\n- Five reasons are reported per rejected server, surfaced as warnings with a skip reason: the entry is foreign, the meta entry is not of type `http`, its URL does not match, no approved startup address exists, or no session id exists.\n- A startup notice tells you MCP servers come only from the verified startup config.\n\n**Evidence**\n\n`was not loaded: the Remote Control meta server entry must be type \"http\"`\n\n- Area: Remote Control\n- Names: `--mcp-config`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}