Repository navigation
v0.25.2
Fixed
-
The MCP server no longer fails to start on a fresh install (#152).
mcpwas pinned as>=1.26.0with no upper bound, so once the SDK published2.0.0— which removed
mcp.server.fastmcp(renamed tomcp.server.mcpserver) —uvx/uvresolved the new major and
cairn.mcp.serverdied on import withModuleNotFoundError: No module named 'mcp.server.fastmcp'.This broke every fresh
uvx agentcairnrun and both the Claude Code and Codex plugins, while
existing installs with a warm uv cache kept working — which is why it went unnoticed. CI could not
catch it either, because it runsuv run --lockedagainst a lockfile pinning mcp 1.28.1; the locked
resolution is not what users get.The dependency is now bounded to
>=1.26.0,<2.0.0. Migrating to the 2.x API (and widening the
bound) is tracked separately.
If you hit this, just upgrade — no workaround needed anymore. The previously required
uvx --with 'mcp<2.0.0' agentcairn is no longer necessary.
Thanks to @fernandomartineztax-pixel for a precise report with a confirmed workaround.