MCP Python SDK 2.2.0 tightens redirects and sessions
The MCP Python SDK published version 2.2.0 on 7 Sep 2026 with changed defaults: HTTP client redirects stay within the endpoint's origin, idle Streamable HTTP sessions expire after 30 minutes, a server holds at most 10,000 sessions, and the OAuth client checks the authorization server's issuer.
Facts read on .
The maintainers' release notes list the behavior changes first. The HTTP client follows a redirect only when it keeps the same scheme, host and port, or upgrades http to https on the same host. Any other redirect fails with an MCPError and the session stays usable. The OAuth providers apply the same rule to their own requests.
For stateful servers on the legacy 2025-11-25 protocol, a session with nothing in flight for 30 minutes is closed, and a server holds at most 10,000 sessions at once. Both limits can be switched off with settings the notes name. The OAuth client now rejects authorization server metadata whose issuer is not the server's own origin on the legacy path too.
The notes also add two deprecation warnings: client-credentials providers without an issuer, and server auth settings that set a resource server URL without choosing whether to validate the token's resource. A later advisory (GHSA-w4fh-qvv9-3v23, 27 Oct 2026) describes the audience gap behind the second warning, so teams running Python MCP servers should read both.
Sources
- MCP Python SDK v2.2.0 release notes (github.com), read
- GHSA-w4fh-qvv9-3v23 advisory (github.com), read