MCP Python SDK v2.0.0 Silently Breaks Projects by Renaming FastMCP to MCPServer

The Model Context Protocol Python SDK released version 2.0.0 on July 28, 2026, renaming its core FastMCP class to MCPServer and relocating all related submodules, with no deprecation warning or backward-compatibility shim. Projects using loosely pinned dependencies in requirements.txt automatically resolved to the new version on fresh installs, causing silent import failures rather than clear error messages. The break only surfaced at runtime, often in CI pipelines or on new contributors' machines, as confirmed by a GitHub issue filed against the jupyter-mcp-server project. A secondary silent change also altered the server's default client-visible name from 'FastMCP' to 'mcp-server' without raising any exception. The incident highlights a broader ecosystem risk, with studies suggesting 20–28% of minor and patch releases introduce breaking API changes, underscoring the importance of strict dependency version pinning.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in