Skip to content

fix: cap mcp dependency to <2 to prevent breaking API changes - #8017

Open
PiedPiper911 wants to merge 1 commit into
microsoft:mainfrom
PiedPiper911:fix-8014-cap-mcp-version
Open

fix: cap mcp dependency to <2 to prevent breaking API changes#8017
PiedPiper911 wants to merge 1 commit into
microsoft:mainfrom
PiedPiper911:fix-8014-cap-mcp-version

Conversation

@PiedPiper911

Copy link
Copy Markdown

Problem

Fixes #8014

The mcp Python SDK released version 2.0.0 with breaking API changes:

  • streamablehttp_client renamed to streamable_http_client
  • Return tuple changed from 3-tuple to 2-tuple
  • read_timeout_seconds changed from timedelta to float
  • camelCase attributes renamed to snake_case (inputSchema -> input_schema, isError -> is_error)

Since autogen-ext declares mcp>=1.11.0 with no upper bound, fresh installs resolve to mcp==2.0.0 and immediately break.

Solution

Cap the dependency at mcp>=1.11.0,<2 in pyproject.toml to prevent automatic upgrade to the incompatible 2.x line.

This is the minimal short-term fix. A full MCP 2.0 migration can be done as a follow-up.

Changes

  • python/packages/autogen-ext/pyproject.toml: Changed mcp>=1.11.0 to mcp>=1.11.0,<2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

autogen-ext: mcp 2.0.0 breaks MCP tools (no upper bound, uses removed/renamed 1.x APIs)

1 participant