Repository navigation
Rewrite the Claude Desktop setup as a step-by-step walkthrough - #16
Merged
Merged
Conversation
Claude Desktop is the client a non-developer athlete is most likely to use, and it had the densest instructions: one paragraph that explained an arg-parsing bug and --allow-http before saying what to do, with no path to the config file, no mention of Node.js, of restarting the app, or of how to tell that it worked. It is now numbered steps (install Node, create a token, open the config, paste, quit and reopen, check), followed by troubleshooting and then the reasons behind the config. The snippet uses an https address by default, with --allow-http as an addition for http addresses inside a tailnet. It says up front that "Add custom connector" does not work with this server. Menu labels, server statuses and the log file naming were checked against Claude Desktop 5.11492.2 on macOS. The Windows paths were not. The dashboard button is "New token", not "Create token"; both mentions are corrected. The reachability note no longer assumes a tailnet.
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
The Claude Desktop part of the README's MCP section is now a numbered walkthrough: install Node.js, create a token, open the config file, paste the entry, quit and reopen, check that it works. Troubleshooting follows, and the reasons behind the config (
${AUTH_HEADER},--allow-http) come last.Why
Claude Desktop is the client a non-developer athlete is most likely to use, and it had the densest instructions in the section. The old paragraph did not say where the config file is, that Node.js is needed, that the app must be fully restarted, or how to tell that the connection works.
Also changed
https://address by default;--allow-httpis an addition forhttp://addresses inside a tailnet.Verification
Menu labels ("Edit config", "View logs"), server statuses (Running / Failed / Not responding) and the
mcp-server-<name>.lognaming were checked against Claude Desktop 5.11492.2 on macOS.Not verified: the Windows paths and tray-quit instruction, and the snippet has not been run end to end with bare
npxand${AUTH_HEADER}.README only; touches a different section than #15.