Skip to content

feat(client): support HTTP auth in ClientSessionGroup #3516

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
musi22 wants to merge 6 commits into
base: main
Choose a base branch
from
Open

feat(client): support HTTP auth in ClientSessionGroup #3516

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
865d13d
feat(client): support HTTP auth in ClientSessionGroup
Sep 17, 2026
c4d7ef2
docs: wrap session group auth example in async function
Sep 17, 2026
2ad805d
test: exercise auth_flow to achieve 100% test file coverage
Sep 17, 2026
0b15b01
test: remove obsolete pragma and isolate session establishment in tests
Sep 17, 2026
741fc75
test: use patch decorators on session tests to prevent python 3.14 br…
Sep 17, 2026
8195fa0
docs(session-groups): add asyncio runner to auth example
Sep 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
docs: wrap session group auth example in async function
  • Loading branch information
Rashmi
Rashmi committed Sep 17, 2026
commit c4d7ef22d91318120873aacb3bca2531c1def186
32 changes: 17 additions & 15 deletions docs/client/session-groups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,21 +78,23 @@ When connecting to HTTP servers using `StreamableHttpParameters` or `SseServerPa
from mcp.client.auth import OAuthClientProvider
from mcp.client.session_group import ClientSessionGroup, StreamableHttpParameters

server_auth = OAuthClientProvider(
server_url="https://api.example.com",
client_metadata=client_metadata,
storage=token_storage,
redirect_handler=redirect_handler,
callback_handler=callback_handler,
)

server_params = StreamableHttpParameters(
url="https://api.example.com/mcp",
auth=server_auth,
)

async with ClientSessionGroup() as group:
await group.connect_to_server(server_params)

async def main() -> None:
Comment thread
cubic-dev-ai[bot] marked this conversation as resolved.
server_auth = OAuthClientProvider(
server_url="https://api.example.com",
client_metadata=client_metadata,
storage=token_storage,
redirect_handler=redirect_handler,
callback_handler=callback_handler,
)

server_params = StreamableHttpParameters(
url="https://api.example.com/mcp",
auth=server_auth,
)

async with ClientSessionGroup() as group:
await group.connect_to_server(server_params)
```

Because `auth` is configured per `ServerParameters` instance, each server in the session group maintains independent authentication context, scopes, and token-refresh lifecycle. Custom headers can still be supplied alongside `auth` via `headers=`.

@cubic-dev-ai cubic-dev-ai Bot Sep 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: When the same auth object is assigned to two parameter instances, ClientSessionGroup shares its mutable OAuth context and tokens. Tell users to construct a distinct auth instance per server before claiming these lifecycles are independent.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At docs/client/session-groups.md, line 98:

<comment>When the same auth object is assigned to two parameter instances, `ClientSessionGroup` shares its mutable OAuth context and tokens. Tell users to construct a distinct auth instance per server before claiming these lifecycles are independent.</comment>

<file context>
@@ -70,6 +70,33 @@ If you already hold a connected `ClientSession` (`Client.session` is one), hand
+    await group.connect_to_server(server_params)
+```
+
+Because `auth` is configured per `ServerParameters` instance, each server in the session group maintains independent authentication context, scopes, and token-refresh lifecycle. Custom headers can still be supplied alongside `auth` via `headers=`.
+
 ## Recap
</file context>
Suggested change
Because `auth` is configured per `ServerParameters` instance, each server in the session group maintains independent authentication context, scopes, and token-refresh lifecycle. Custom headers can still be supplied alongside `auth` via `headers=`.
Because `auth` is configured per `ServerParameters` instance, give each server a distinct auth instance to maintain independent authentication context, scopes, and token-refresh lifecycle. Custom headers can still be supplied alongside `auth` via `headers=`.

Expand Down
Loading