Repository navigation
v0.1.14
Fixed
-
Works with the mcp SDK 2.x (#3). The server registered its two handlers
through the 1.x decorator API (@app.list_tools()/@app.call_tool()),
which mcp 2.0 removed, so with mcp ≥ 2.0 installedimport nodus_mcp_server.serverfailed — both transports. 0.1.13 pinnedmcp<2as
the stopgap; the pin is lifted tomcp>=1.8.One implementation with a branch per SDK major, chosen once at import
(_SDK_V2): on 2.x the handlers go throughadd_request_handler, take
(ctx, params)and return result models; 1.x is unchanged. The same port as
nodus-mcp 0.1.4 (nodus-mcp#11), so the two servers do not drift. Both
branches are driven bytests/test_http_transport.py's realinitialize→
tools/listthrough the ASGI app: 27/27 under mcp 1.27 and under 2.2.