Repository navigation
Preserve backend HTTP status in MCP errors - #33
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
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.
What changed
chooseandchooseManytool errors without exposing upstream messages or bodies.choosekit^0.9.1 and preparechoosekit-mcp0.6.1.Why
MCP clients currently receive the same error message for an invalid API key (HTTP 401), rate limiting (HTTP 429), and an unavailable backend (HTTP 503). Including the status code makes these failures distinguishable without exposing the backend response body.
Checks
npm run check— core: 195 tests, MCP: 37 testsnpm pack --dry-run— both packagesgit diff origin/master...HEAD --check