Skip to content

fix(python-servers): cap mcp version below v2.0.0 to prevent startup … - #4645

Open
KavyaNagariya wants to merge 1 commit into
modelcontextprotocol:mainfrom
KavyaNagariya:fix/cap-mcp-v1-python-servers
Open

fix(python-servers): cap mcp version below v2.0.0 to prevent startup …#4645
KavyaNagariya wants to merge 1 commit into
modelcontextprotocol:mainfrom
KavyaNagariya:fix/cap-mcp-v1-python-servers

Conversation

@KavyaNagariya

@KavyaNagariya KavyaNagariya commented Aug 15, 2026

Copy link
Copy Markdown

Description

This PR caps the mcp SDK dependency to <2.0.0 for all Python-based reference servers (fetch, git, and time).

Because the Python MCP SDK recently released version 2.0.0 with breaking changes (renaming McpError to MCPError and removing decorators like @server.list_tools()), unpinned installations like uvx mcp-server-git would resolve the latest 2.0.0 version and instantly crash on startup. Capping the dependencies ensures these servers continue to run properly on older stable SDK APIs.

Server Details

  • Server: fetch, git, time
  • Changes to: pyproject.toml dependencies

Motivation and Context

This resolves three active startup crash issues:

How Has This Been Tested?

Tested locally by compiling the package and verifying that the dependency resolution caps the mcp SDK below 2.0.0.

Breaking Changes

No (prevents breaking changes introduced by the SDK upgrade).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally

@KavyaNagariya
KavyaNagariya force-pushed the fix/cap-mcp-v1-python-servers branch from b0c96ef to 8959005 Compare August 15, 2026 06:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant