MCP Python SDK v2.2.0
MCP Python SDK releases published MCP Python SDK v2.2.0. pip install -U mcp . Docs: https://py.sdk.modelcontextprotocol.io/ A few defaults changed in this release. If you run a server or client on 2.x, skim these first: Behaviour changes HTTP client redirects are only followed within the endpoint's origin ( 3397 ) Client("https://...") , streamable http…
Why this signal matters
MCP Python SDK releases published MCP Python SDK v2.2.0. This release-watch entry was generated from the project's official GitHub release feed and is kept separate from human-reviewed editorial analysis. Release notes: pip install -U mcp . Docs: https://py.sdk.modelcontextprotocol.io/ A few defaults changed in this release. If you run a server or client on 2.x, skim these first: Behaviour changes HTTP client redirects are only followed within the endpoint's origin ( 3397 ) Client("https://...") , streamable http client and sse client follow a redirect only if it stays on the same scheme, host and port (or upgrades http to https on the same host). A redirect anywhere else is not followed: the call fails with MCPError and the session stays usable (an SSE connect fails with httpx2.HTTPStatusError ). If that other URL is the server you meant, use it as the endpoint URL. The follow redirects setting on an httpx2.AsyncClient you pass in is no longer used for MCP requests, so you don't need it for the trailing-slash redirect any more. The OAuth providers apply the same rule to their own requests. Idle…
Actionable summary
Treat MCP Python SDK v2.2.0 as an official release signal. Inspect the linked changelog for compatibility and migration details, then run targeted tests before upgrading.
- Agent usefulness
- 82/100
- Confidence
- 96%
- Canonical data
- JSON + Markdown
What builders should check
- Review the official MCP Python SDK releases release notes before upgrading.
- Check compatibility, migration, and security notes against your current agent stack.
- Run focused regression tests before production rollout.