jif e19e65317a Reuse MCP connections across runtime refreshes (#34952) ...

## Why

Refreshing MCP runtime state should not restart an unchanged, ready server or
relist its tools.

## What changed

- Reconcile refreshed MCP configuration against the published connection set
  and reuse connections whose transport, environment, authentication, OAuth
  credentials, and client capabilities are unchanged.
- Keep tool filters, timeouts, metadata, and plugin provenance in the published
  server view so those settings can change without reconnecting.
- Update elicitation authority in place for reused connections, and reconnect
  when connection-defining inputs or live OAuth credentials change.

## Testing

Added coverage for unchanged-server reuse, view-only and elicitation-policy
updates, connection identity changes, OAuth credential changes, and avoiding
redundant tool listing.

GitOrigin-RevId: f04f5db5fbdde127b6a14f6aa9673112c0b557e7

2026-07-23 14:55:31 +00:00

..

src

Add batched executor capability discovery (#33852)

2026-07-17 15:45:48 +00:00

tests

Reuse MCP connections across runtime refreshes (#34952)

2026-07-23 14:55:31 +00:00

BUILD.bazel

Route hosted Apps MCP through extensions (#27191)

2026-06-09 22:44:16 +02:00

Cargo.toml

Add batched executor capability discovery (#33852)

2026-07-17 15:45:48 +00:00