Repository navigation
Upgrade to FastMCP 4 for MCP discovery support - #11
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
uv.lock.2026-07-28discovery and tool listing, plus legacy2025-11-25initialization and tool listing.Why
Recent Claude clients probe
server/discover. The FastMCP 3 / MCP 1 runtime rejects it before Conduit handles the request, producing repeated 31-error validation warnings even when clients fall back and tools work. FastMCP 4 supports the new protocol while retaining the legacy handshake.Validation
pytest -m 'not integration' -q: 395 passed, 87 deselected, 2 subtests passed.ruff check .,ruff format --check ., and Bandit passed.server/discoversucceeds withsupportedVersions: ["2026-07-28"]; legacyinitializesucceeds with2025-11-25.Live Phorge integration tests were not run locally because no test container is running. CI will also build and smoke-test the release Dockerfile.
Rollout
After merge, publish a versioned GHCR image and deploy that explicit tag. Confirm the discovery warning stops while Claude tool calls continue to work. The previously deployed
0.0.6image tag remains the rollback target.