fix(deps): cap mcp below 2 so uvx uns_mcp starts
VI
11d ago+10+10+01234567890123456789-4-4-0123456789
Problem
The README's Claude Desktop setup runs uvx uns_mcp. Both pyproject.toml and the published uns_mcp 0.1.8 on PyPI ask for mcp[cli]>=1.13.1 with no upper bound, and uvx doesn't read uv.lock, so a fresh run now gets mcp 2.3.0. uns_mcp/server.py line 14 does from mcp.server.fastmcp import Context, FastMCP. mcp 2.x removed that module, so the server fails on import:
ModuleNotFoundError: No module named 'mcp.server.fastmcp'
uv sync from a checkout isn't affected, because uv.lock pins mcp 1.26.0.
Change
mcp[cli]>=1.13.1,<2inpyproject.toml, and the matchingrequires-distline inuv.lock. No locked package changes.- Version 0.1.9 and a CHANGELOG entry, following #77. The
uvxpath only gets the fix from a new PyPI release, andrelease.ymlpublishes when the version changes, so merging this will publish 0.1.9. If you'd rather release separately, tell me and I'll drop the bump.
Moving to the 2.x API can be a separate change.
Checked
fresh resolve (uv pip compile, Python 3.12) | mcp.server.fastmcp at that version | |
|---|---|---|
| main | mcp==2.3.0 | absent from the v2.3.0 tag |
| this branch | mcp==1.30.0 | present in the v1.30.0 tag |
uv lock --check passes on this branch. I also ran from mcp.server.fastmcp import FastMCP in clean environments: it works on mcp 1.30.0 and fails on 2.3.0 with ModuleNotFoundError. I did not run the server end to end.