MCP URLs from the cloud bridge must match your own session route or they're dropped.
What's wrong with this entry?
The MCP server URL handed over by the cloud bridge previously only had to sit on the bridge's origin. It now has to be this session's own proxy route or it is dropped with a warning, closing off a bridge-supplied URL pointing at another session or a crafted path.
- The URL must parse to that exact origin, carry no credentials and no fragment, and match the
/v2/ccr-sessions/<sessionId>/mcppath for the current session. - Only allow-listed query parameters are permitted, with a fixed toolbox server id.
- The nested inner URL must itself be the canonical path on the same origin, and the server id must match a fixed pattern.
[bridge:server-config] meta url is not this session's meta proxy route on the bridge origin
Strings lifted out of the shipped bundle, so the claim above can be checked against them.