docs: brew relink step after in-app update to v0.6.0#9
Merged
Conversation
Homebrew users who installed 0.5.1 and let the app self-update reach 0.6.0 without the docsreader-mcp PATH symlink, so the bare-command MCP registration fails with ENOENT. Tell them to run brew upgrade once, and point out that the in-app Connect flow writes the full binary path and is unaffected.
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.
brew upgrade --cask docsreaderso Homebrew linksdocsreader-mcponto PATH; the in-app Connect flow writes the full binary path and is unaffectedWithout the relink, the documented bare-command registration (
claude mcp add ... -- docsreader-mcp) fails with ENOENT for that cohort.