Add --prefer-online to prevent stale MCP server cache#7
Merged
critesjosh merged 2 commits intomainfrom Mar 4, 2026
Merged
Conversation
1 task
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
--prefer-onlineflag to npx args in.mcp.jsonso npx checks the npm registry before falling back to its local cache@aztec/mcp-serverversions because npx resolves@latestonce and caches it indefinitelyContext
After
@aztec/mcp-server@1.11.0was published (with sync metadata from AztecProtocol/mcp-server#8), users with a cached1.10.0never see the update unless they manually clear~/.npm/_npx/.Test plan
npx --prefer-online -y @aztec/mcp-server@latestlaunches correctly on npm 11.6.2 / Node 24Closes #6
🤖 Generated with Claude Code