Update dependency mcp to v2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
mcp	>=1.0,<2 → >=1.0,<3

---

Release Notes

modelcontextprotocol/python-sdk (mcp)

v2.2.0

Compare Source

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 Streamable HTTP sessions now expire (legacy <=2025-11-25 spec( (#​3395)

• A stateful session with nothing in flight for 30 minutes is closed. The client's next request gets a 404 and it has to initialize again.
• Clients that keep the GET stream open (the SDK's Client does) are not affected. Neither are stateless servers or 2026-07-28 connections.
• A server also holds at most 10 000 sessions at once; beyond that, new sessions get a 503.
• To turn either off: mcp.run(transport="streamable-http", session_idle_timeout=None, max_sessions=None) (also on streamable_http_app() and run_streamable_http_async()).

The OAuth client checks the authorization server's issuer on the legacy path too (#​3398)

• For servers without protected resource metadata, authorization server metadata whose issuer isn't the server's own origin is now rejected with OAuthFlowError: Authorization server metadata issuer mismatch. The protected-resource-metadata path has done this since 2.0.
• A 403 that isn't an insufficient_scope challenge is returned to the caller instead of retried.
• If protected resource metadata can't be fetched because of a 5xx/429, the flow now stops instead of falling back to the legacy endpoints.

Two new MCPDeprecationWarnings (#​3435, #​3447)

• ClientCredentialsOAuthProvider / PrivateKeyJWTOAuthProvider without issuer=. Pass your authorization server's issuer URL; 3.0 will require it.
• AuthSettings with resource_server_url set but validate_token_resource unset. Set it to True or False; 3.0 defaults it to True.
• Both keep working as before in 2.x; this mostly matters if your tests turn warnings into errors.

New

• AuthSettings.validate_token_resource: only accept tokens your TokenVerifier reports as issued for this server (#​3447).
• issuer= on ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider (#​3398).
• session_idle_timeout= and max_sessions= on the Streamable HTTP server entry points (#​3395).

Fixes

• A client DELETE frees its session immediately, and a refused opening request no longer leaves a session behind (#​2455, #​3228, #​3300).
• $refs in a tool's outputSchema resolve within that schema only; an unresolvable one surfaces as RuntimeError: Invalid schema for tool ... (#​3394).

Known gaps

The tasks extension (SEP-2663), DPoP (SEP-1932) and the jwt-bearer grant are not implemented yet; https://github.com/modelcontextprotocol/python-sdk/blob/main/ROADMAP.md tracks them.

What's Changed

• Gate draft PRs too and rewrite the auto-close comment by @​maxisbey in #​3378
• Resolve tool output-schema references within the schema document only by @​maxisbey in #​3394
• Expire idle Streamable HTTP sessions by default and cap concurrent sessions by @​maxisbey in #​3395
• Validate the authorization server metadata issuer on every discovery path by @​maxisbey in #​3398
• Deprecate constructing the pre-provisioned OAuth clients without an issuer by @​maxisbey in #​3435
• Exercise the SEP-2575 stateless probes and SEP-2243 resource/prompt headers in the conformance fixtures by @​maxisbey in #​3442
• Bump the github-actions group with 6 updates by @​dependabot[bot] in #​3424
• Move the docs-preview workflow scripts out of the YAML into .github/scripts by @​maxisbey in #​3446
• Skip automatic docs previews for fork PRs and drop the setup-uv retry steps by @​maxisbey in #​3445
• Follow redirects only within the MCP endpoint's origin by @​maxisbey in #​3397
• Bump pymdown-extensions from 11.0 to 11.0.1 by @​dependabot[bot] in #​3285
• Bump the locked versions of eight dev and test dependencies by @​maxisbey in #​3449
• Keep following a relative redirect when the endpoint URL carries userinfo by @​maxisbey in #​3450
• Add AuthSettings.validate_token_resource to check a bearer token's resource by @​maxisbey in #​3447
• docs: stop presenting the in-memory client as the way to connect by @​maxisbey in #​3443
• docs: ask for AI disclosure on comments too by @​maxisbey in #​3459
• docs: refresh translations, and translate pages in parallel by @​maxisbey in #​3458
• Replace RootModel wrappers with type aliases and TypeAdapter validation by @​Kludex in #​3470

Full Changelog: modelcontextprotocol/python-sdk@v2.1.1...v2.2.0

v2.1.1

Compare Source

What's Changed

• Point imports of mcp.server.fastmcp at the migration guide by @​maxisbey in #​3388

Full Changelog: modelcontextprotocol/python-sdk@v2.1.0...v2.1.1

v2.1.0

Compare Source

Highlights

• Client accepts StdioServerParameters directly: Client(StdioServerParameters(command="uv", args=["run", "server.py"])) (#​3321).
• Prompt messages accept Image and Audio, prompt functions may return bare content blocks, and Message / UserMessage / AssistantMessage are exported from mcp.server.mcpserver (#​3320).
• The 4 MiB request body limit now also covers the SSE transport and the OAuth endpoints; SseServerTransport and MCPServer.sse_app() take max_request_body_size, and the SSE message endpoint answers 405 to non-POST requests (#​3336).

Behaviour changes to be aware of

• Handler exceptions (#​3314): an unexpected exception from a tool, resource or prompt handler is logged once at ERROR with its traceback, and the client now sees only Error executing tool <name> (or the resource/prompt equivalent) rather than the exception text. Raise ToolError / ResourceError when the message is meant for the model; those still reach the client and are logged at INFO without a traceback.
• Content-block return annotations (#​3320): a tool annotated to return TextContent, EmbeddedResource, Image, Audio, or lists/unions of them no longer advertises outputSchema or returns structuredContent; its content is unchanged. Pass structured_output=True to keep the previous shape.

Fixes

• TypedDict tool results: NotRequired keys are omitted instead of serialized as null, and registration no longer fails on Python 3.10 (#​3224, #​3227); recursive return types get an object-rooted outputSchema that pre-2026 clients accept (#​3337).
• 2026-07-28 over HTTP: a POSTed notification such as notifications/cancelled is acknowledged with 202 instead of rejected with 400 (#​3324).
• Pre-2026 sessions ignore cache-hint fields from later revisions instead of failing list_tools() (#​3223), and accept boolean sub-schemas in tool schema properties (#​3353).
• mcp install reads and preserves a Claude Desktop config containing non-ASCII text on any Windows code page (#​3296).

What's Changed

• Retire wording tied to pre-2.0 milestones by @​maxisbey in #​3211
• Describe the maintenance line without hardcoding 1.28 by @​maxisbey in #​3212
• Ask which release line a bug report is on by @​maxisbey in #​3213
• Link the released 2026-07-28 spec and point migrators at /v1/ by @​maxisbey in #​3214
• Bump conformance harness to 0.2.0-alpha.11 by @​maxisbey in #​3282
• Read UTF-8 test fixtures with explicit encoding by @​ShuQingDollarVoyager in #​3245
• Pin each conformance leg to a spec-revision wire by @​maxisbey in #​3304
• docs: publish translated docs in twelve languages and the tool that maintains them by @​maxisbey in #​3280
• Pin text I/O to UTF-8 and fail CI on locale-dependent reads/writes by @​maxisbey in #​3296
• docs: lead the README client example with a URL, not the server object by @​maxisbey in #​3315
• Publish versioning, roadmap, and dependency policies for v2 by @​maxisbey in #​3215
• Drop later-revision cache-hint fields on pre-2026 sessions by @​maxisbey in #​3223
• Stop framing breaking changes as a workflow in AGENTS.md by @​maxisbey in #​3286
• MCPServer: content-block returns are unstructured, prompt messages take Image/Audio by @​maxisbey in #​3320
• Let Client take StdioServerParameters directly by @​maxisbey in #​3321
• Gate external PRs on an assigned, linked issue by @​maxisbey in #​3291
• docs: cover the remaining Tier 1 audit items by @​maxisbey in #​3325
• Acknowledge notification POSTs with 202 on the 2026-07-28 HTTP entry by @​maxisbey in #​3326
• Shorten stdio test comments by @​Kludex in #​3329
• Hand TypedDict tool results to pydantic natively by @​maxisbey in #​3331
• Apply the request body limit to the SSE and OAuth endpoints by @​maxisbey in #​3336
• Accept boolean sub-schemas in 2025-11-25 tool schema properties by @​pja-ant in #​3354
• Log MCPServer handler exceptions by kind and keep crash details off the wire by @​maxisbey in #​3314
• Give recursive tool return types an object-rooted output schema by @​maxisbey in #​3376
• docs: refresh translations for recent English changes by @​maxisbey in #​3379
• Build releases with the pinned hatchling and a publish action that accepts Metadata 2.5 by @​maxisbey in #​3380

New Contributors

• @​ShuQingDollarVoyager made their first contribution in #​3245

Full Changelog: modelcontextprotocol/python-sdk@v2.0.0...v2.1.0

v2.0.1

Compare Source

One off backport of the FastMCP import warning for 2.0.x, this is due to a lot of people running into this error and making issues on other repos about it. Ideally either pin mcp<2 or upgrade to 2.

What's Changed

• [v2.0.x] Point imports of mcp.server.fastmcp at the migration guide by @​maxisbey in #​3393

Full Changelog: modelcontextprotocol/python-sdk@v2.0.0...v2.0.1

v2.0.0

Compare Source

MCP Python SDK v2 Stable Release

This is v2.0.0, the stable v2 release of the MCP Python SDK. It supports the 2026-07-28 revision of the Model Context Protocol and serves every earlier revision from the same server. pip install mcp now installs 2.x.

pip install "mcp[cli]"

# or
uv add "mcp[cli]"

Documentation Rewrite

The documentation has the full tutorial and API reference. Coming from v1? What's new in v2 is the tour of what changed and why, and the migration guide lists every breaking change with before-and-after code.

V1 Maintenance mode

v1.x is in maintenance mode and will only receive security fixes from now on The 1.x line lives on the v1.x branch, continues to receive critical bug fixes and security patches, and is documented at https://py.sdk.modelcontextprotocol.io/v1/. If your project is not ready to migrate, keep a <2 upper bound on your requirement (for example mcp>=1.28,<2).

Highlights

One SDK, both protocol eras

v2 speaks the 2026-07-28 revision (stateless requests with no handshake, server/discover, subscriptions/listen, multi-round-trip requests) and still serves every 2025-era client from the same MCPServer, over Streamable HTTP and stdio, with nothing to configure. Client(target) negotiates the version automatically.

FastMCP is now MCPServer, and there is a first-class Client

The decorator API is unchanged; the low-level Server is rebuilt around a shared dispatcher engine, and one Client object replaces v1's transport-plus-ClientSession-plus-initialize() layering. It connects to a URL, a stdio subprocess, a custom transport, or straight to a server object in memory for tests.

Multi-round-trip requests and resolver dependency injection

At 2026-07-28 the server can no longer call the client, so tools return the question instead. A Resolve(fn) parameter is filled by your function invisibly to the model and can put a question to the user; one tool body serves both eras.

Extension APIs, OpenTelemetry, and a standalone types package

Servers and clients compose protocol extensions through pluggable extension APIs (MCP Apps built in); OpenTelemetry tracing ships on by default; every protocol type is its own package, mcp-types (imported as mcp_types), published in lock-step with mcp.

Hardened stdio and auth

stdio servers keep handler subprocesses and stray prints off the wire, and stdout is diverted to stderr while serving. OAuth adds RFC 9207 issuer validation, the SEP-990 identity-assertion flow, and the client-credentials extension.

Coming from a v2 pre-release

Since the last release candidate: the per-version wire packages are private (mcp_types._v*), mcp.types is a permanent alias for mcp_types, the auth registration request model is split from the registered-client record, cancelled requests are no longer answered, and log notifications are gated on the per-request log-level opt-in at 2026-07-28. Since the betas: Client(cache=False) is now cache=None with CacheConfig() the default; Context.client_id, RFC7523OAuthClientProvider, and OAuthClientProvider(timeout=) are removed; the client-credentials providers take scope=; message_handler receives notifications and exceptions only; FileResource(is_binary=) becomes encoding; MCP_* env vars are gone with pydantic-settings; Streamable HTTP servers reject bodies over 4 MiB with HTTP 413. The migration guide covers all of it.

Known gaps

The tasks extension (SEP-2663) is not part of this release. On the client, the DPoP proof binding (SEP-1932) and the workload-identity jwt-bearer grant are not implemented; both are additive and can land in 2.x.

Feedback

Something rough, confusing, or broken? Open an issue or find us in #python-sdk-dev on the MCP Contributors Discord.

Full Changelog: modelcontextprotocol/python-sdk@v2.0.0rc1...v2.0.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.72%. Comparing base (5e9dce5) to head (7dc6131).

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #313       +/-   ##
===========================================
+ Coverage   64.78%   78.72%   +13.94%     
===========================================
  Files          27       27               
  Lines        1133     1133               
===========================================
+ Hits          734      892      +158     
+ Misses        399      241      -158     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.