New JSON Schema Requirement Bumps with LiteLLM

[rawkintrevo]

Initial Checks

• I confirm that I'm using the latest version of MCP Python SDK
• I confirm that I searched for my issue in https://github.com/modelcontextprotocol/python-sdk/issues before opening this issue

Description

On this commit,
c8bbfc0#diff-50c86b7ed8ac2cf95bd48334961bf0530cdc77b5a56f852c5c61b89d735fd711R34

A new dependency was added "jsonschema==4.20.0" authored by @bhosmer-ant

The issue is the hard req on 4.20.0 bumps with LiteLLM

I don't see any notes in the PR that 4.20.0 precisely needs to be used. Changing it to >= anecdotally works in my case.

LiteLLM is a pretty popular package, would be nice to maintain compatibility.

The conflict is caused by:
    mcp 1.9.5.dev23+c8bbfc0 depends on jsonschema==4.20.0
    litellm 1.73.1 depends on jsonschema<5.0.0 and >=4.22.0
    litellm 1.73.0 depends on jsonschema<5.0.0 and >=4.22.0
    litellm 1.72.9 depends on jsonschema<5.0.0 and >=4.22.0

It goes on like this back to 1.72.0 released may 31, at least.

Example Code

Python & MCP Python SDK

Python 3.11
mcp 1.9.5.dev23+c8bbfc0

[rawkintrevo]

Note, I'm not blocked in anyway- version pinning to commit hash 0b11bdb6297ce works fine for me, just a heads up before the release is cut*