best-mcp: make the client version model-visible - #12
Merged
Conversation
serverInfo.version (fixed in 2.3.1) reaches the HOST, never the model -
so "what version of best-mcp are you using?" was still unanswerable in
chat and the agent fell back to the server''s spec version. The package
version now rides the two places the model can actually read:
- the initialize instructions ("connected through the
@behavioralstate/best-mcp client, version X.Y.Z"), with an explicit
note that a manifest''s version is the BEST SPEC version - a different
thing;
- the get_manifest result, as a leading `client` field.
Both read the real package.json version, so release bumps propagate
with no code change. Verified over stdio.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
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.
Follow-up to the serverInfo.version fix (2.3.1): hosts read serverInfo, models don''t - so "which best-mcp is this?" was still unanswerable in chat (the agent answered with the server''s spec version instead). The package version now rides the two surfaces the model can read:
clientfield.Both derive from package.json at runtime, so release bumps propagate automatically. Verified over stdio (instructions line + manifest field present).
tscclean.Release after merge:
LC_ALL=en_US.UTF-8 ./scripts/release-mcp.sh 2.3.3.🤖 Generated with Claude Code