fix(deps): hold mcp below 2.0 until the MCPServer rename is done - #32
Merged
Conversation
mcp 2.0.0 shipped and renamed mcp.server.fastmcp to mcp.server.mcpserver, along with FastMCP to MCPServer. Every tool module imports the old path, so pip resolving the open-ended >=1.0 to 2.0 broke collection of four test modules on main and on every open PR. Cap at <2 to get CI reporting again. 1.29.0 is the newest 1.x and still ships mcp.server.fastmcp, so the ceiling costs nothing today. Migrating to the 2.0 API is separate work.
This was referenced Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pourquoi
mcp2.0.0 est sorti et a renommémcp.server.fastmcpenmcp.server.mcpserver, ainsi queFastMCPenMCPServer. La dépendance était déclaréemcp[cli]>=1.0, sans borne haute, donc la CI a installé la 2.0 dès sa publication et quatre modules de test ne collectent plus :mainest rouge sur les trois versions de Python, et toutes les PR ouvertes héritent de la panne. Rien à voir avec leur contenu.Changement
Une ligne :
mcp[cli]>=1.0,<2.La 1.29.0 est la dernière 1.x et expose toujours
mcp/server/fastmcp/__init__.pyavecFastMCP, donc le plafond ne coûte rien aujourd'hui et la CI récupère du signal utile.Ce que ça ne fait pas
Ça ne migre pas vers l'API 2.0. Le renommage touche chaque module d'outils (
proxmox/,ssh/,bmc/,server.py) et la surface deMCPServerdiffère au-delà du chemin d'import, donc c'est un travail séparé à faire volontairement, pas un remplacement d'imports.