fix: cap mcp below 2.0 to stop silent no-op server fallback (0.4.1) #5
Loading…
Reference in a new issue
No description provided.
Delete branch "develop"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
mcp2.x renamedFastMCPtoMCPServerand moved the module.app/server.py'sexcept ImportErrorfallback (meant for "SDK not installed" in dev/test) was silently catching that too and swapping in a no-op stub server, so unpinned installs (Dockerfile and CI both do a barepip install .) were shipping a server where every tool/resource/prompt is inert.mcp[cli]to>=1.28.1,<2to stop that, regeneratedrequirements-lock.txtagainst the capped constraint, and removed the unuseduv.lock(stale since the initial commit; the project uses pip viaTaskfile.yml, never uv).ruff/mypydev floors with the pre-commit revs (they had drifted) and addedPLR0917to the ruff ignore list (new rule surfaced by the ruff bump, same rationale as the existingPLR0913ignore).CHANGELOG.mdentry.Test plan
pytest tests/— 312 passedruff check/ruff format --check— cleanmypy app/ tests/— cleanbandit -r app/— no issuesfrom mcp.server.fastmcp import FastMCPsucceeds andapp.server.mcpis the realTypedFastMCPwrapper (not the fallback stub) with the capped constraint🤖 Generated with Claude Code
https://claude.ai/code/session_01T7TeYpy6hK7de1bAghSSjU