From 5581e37ed3f497a3e055119db46c7689fd0841ec Mon Sep 17 00:00:00 2001 From: Showdown76py Date: Wed, 29 Jul 2026 05:03:49 +0200 Subject: [PATCH] fix(deps): hold mcp below 2.0 until the MCPServer rename is done 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. --- pyproject.toml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index 69e7b94..a18ee64 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -8,7 +8,11 @@ version = "2.0.0" description = "Remote MCP server for Proxmox VE and BMC (iLO/IPMI) infrastructure management" requires-python = ">=3.11" dependencies = [ - "mcp[cli]>=1.0", + # 2.0 renamed mcp.server.fastmcp to mcp.server.mcpserver and FastMCP to + # MCPServer, which every tool module imports. Hold at 1.x until that + # migration lands; the range was open-ended, so CI started installing + # 2.0 the day it shipped and stopped collecting four test modules. + "mcp[cli]>=1.0,<2", "proxmoxer", "requests", "python-hpilo",