thomas 6baa076eb6 Allow extensions to select MCP protocol mode per HTTP server (#44571) ...

## Why

Extension-owned HTTP MCP servers previously inherited the default protocol mode. Extensions need to select a mode for their own server independently of other HTTP servers.

## What changed

- Add `McpServerContribution::SetWithProtocolMode` and re-export `McpProtocolMode` through the extension API.
- Carry the winning registration's protocol override through catalog resolution and materialization, and apply it to Streamable HTTP connections.
- Preserve existing defaults when no override is present. Selecting a protocol mode does not grant host-owned Apps cache access or environment authority.

## Testing

Add coverage for registration precedence and materialization, and extend cache isolation tests to cover explicit protocol selection. Add an integration test verifying that extension servers can select either the legacy or newer protocol while other HTTP servers retain the default mode.

GitOrigin-RevId: 606cecc03094a93258ffc433849f575020b81473

2026-09-10 16:02:59 +00:00

..

src

Allow extensions to select MCP protocol mode per HTTP server (#44571)

2026-09-10 16:02:59 +00:00

BUILD.bazel

Support package-style MCP server names (#41700)

2026-08-30 16:45:34 +00:00

Cargo.toml

Support package-style MCP server names (#41700)

2026-08-30 16:45:34 +00:00