Remote Control bridge children reject foreign --mcp-config servers and rebuild the meta server themselves.
What's wrong with this entry?
A 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.
- 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. - A startup notice tells you MCP servers come only from the verified startup config.
was not loaded: the Remote Control meta server entry must be type "http"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Feedback dialog drops the "Drafted by Claude" line
Both mention config
-
v2.1.247
Enter in /config acts on the row you are actually on
Both mention config
-
v2.1.248
Project settings can no longer redirect your config directory
Both mention config