v0.2.3 supports both mcp SDK majors via small dual-path compat layers (lean_memory._mcp_compat, lean_memory_console._mcp_compat, tests/mcp_client_compat.py), pin mcp>=1.2,<3. That's the right call one day into the 2.0 ecosystem, but the 1.x path should eventually go.
Signal to watch (recorded in docs/superpowers/workpackets.md § WP12): major MCP clients/frameworks flooring at mcp>=2, or the 1.x branch stopping security fixes.
When it fires: floor at mcp>=2,<3, delete the three compat branches (the v2 arms become the only code), update the pyproject guard test, changelog under Changed. Until then both paths stay covered — dev venvs on 1.x, CI fresh-resolve on 2.x.
v0.2.3 supports both mcp SDK majors via small dual-path compat layers (
lean_memory._mcp_compat,lean_memory_console._mcp_compat,tests/mcp_client_compat.py), pinmcp>=1.2,<3. That's the right call one day into the 2.0 ecosystem, but the 1.x path should eventually go.Signal to watch (recorded in
docs/superpowers/workpackets.md§ WP12): major MCP clients/frameworks flooring atmcp>=2, or the 1.x branch stopping security fixes.When it fires: floor at
mcp>=2,<3, delete the three compat branches (the v2 arms become the only code), update the pyproject guard test, changelog under Changed. Until then both paths stay covered — dev venvs on 1.x, CI fresh-resolve on 2.x.