From 143d7e7329cabab5dba02efc04630e5ce8f5e484 Mon Sep 17 00:00:00 2001
From: Mateo Wang <277851410+mateo-berri@users.noreply.github.com>
Date: Tue, 23 Jun 2026 22:59:10 -0700
Subject: [PATCH] docs(mcp): correct the bridge docstring now that the graft is
 wired

adapter.py's module docstring still said the bridge was unwired; _create_mcp_client
now calls to_server_spec, to_subject, and raise_public on the HTTP/SSE path, so the
docstring says that
---
 .../_experimental/mcp_server/outbound_credentials/adapter.py   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/litellm/proxy/_experimental/mcp_server/outbound_credentials/adapter.py b/litellm/proxy/_experimental/mcp_server/outbound_credentials/adapter.py
index 39db2314aee..7ad1c5eb2aa 100644
--- a/litellm/proxy/_experimental/mcp_server/outbound_credentials/adapter.py
+++ b/litellm/proxy/_experimental/mcp_server/outbound_credentials/adapter.py
@@ -3,7 +3,8 @@
 These edge functions translate v1's request objects into the resolver's typed inputs and map
 its typed errors onto the proxy's public exception contract. They import v1 and live outside the
 package's public surface so the resolver core (``resolver.py`` / ``types.py``) stays v1-free.
-Nothing wires them into ``_create_mcp_client`` yet.
+``_create_mcp_client`` calls them on the HTTP/SSE path: it resolves a migrated mode through the
+provider and defers every other mode to v1.
 
 ``to_server_spec`` maps only the modes the resolver has gone live for, returning ``None`` for
 every other mode so the caller defers to v1 (parity-safe); it grows one branch per migrated mode.