modelcontextprotocol/python-sdk
Watch
1
0
Fork
You've already forked python-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Link the released 2026-07-28 spec and point migrators at /v1/ (#3214)

Browse source
This commit is contained in:
Max 2026-07-29 15:01:27 +01:00 • committed by GitHub
commit a4f4ccd091
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/migration.md
View file

@ -4,6 +4,11 @@ This guide covers the breaking changes introduced in v2 of the MCP Python SDK an
Version 2 of the MCP Python SDK introduces several breaking changes to improve the API, align with the MCP specification, and provide better type safety.
!!! note "Not ready to migrate yet?"
The v1.x maintenance line keeps receiving critical bug fixes and security patches, and its
documentation is at [/v1/](https://py.sdk.modelcontextprotocol.io/v1/). If your package depends
on `mcp`, keep a `<2` upper bound until you've migrated.
## Find your changes
Every section heading below names the API it affects, so searching this page for the symbol your code uses is the fastest route to the change that broke it. The guide lists changes only: an SDK API not mentioned here behaves as it did in v1, and the "what did not change" summaries — [`MCPServer`](#what-is-unchanged-on-mcpserver), [lowlevel `Server`](#lowlevel-server-what-did-not-change), and [auth](#unchanged-auth-surfaces) — spell out the surfaces most migrators stop to check.