Repository navigation
docs: add Desktop Commander MCP setup guide - #5
Closed
Protonmatter wants to merge 1 commit into
Closed
Protonmatter wants to merge 1 commit into
Protonmatter wants to merge 1 commit into
Conversation
Document attaching the Desktop Commander MCP server to the two clients used with this repository, and record why the transport differs between them. - docs/DESKTOP_COMMANDER.md: local stdio setup for the Claude Code CLI, remote relay device setup (`npx ... remote`) for cloud-hosted sessions such as Cowork, flag reference, uninstall, and the operational boundary against Project-Her's read-only MCP server. - .mcp.json.example: copyable config pinning both `project-her` and `desktop-commander`. The live .mcp.json is gitignored so an unrestricted shell server stays opt-in per user rather than prompting everyone who clones the repository. - Cross-link from README.md and docs/PROJECT_HER.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AAzsKTVzsQaiJR6BDCmvpV
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.
Summary
Documents how to attach the Desktop Commander MCP server (
@wonderwhy-er/desktop-commander) to the Claude Code CLI and to cloud-hosted Claude sessions such as Cowork, and records why the transport differs between the two.The core distinction: which subcommand you need depends on where the model runs, not on the product name. A local client spawns the server over stdio; a cloud-hosted session cannot reach your machine that way and needs the
remoterelay device instead.Changes
docs/DESKTOP_COMMANDER.md(new) — local stdio setup for the Claude Code CLI, remote relay device setup (npx ... remote) for cloud sessions, flag reference (--persist-session,--disable-no-sleep,--debug), uninstall path, and the operational boundary against Project-Her's own MCP server..mcp.json.example(new) — copyable config pinning bothproject-heranddesktop-commander..gitignore— ignore the live.mcp.json.README.md,docs/PROJECT_HER.md— cross-links to the new guide.Notes on the design decisions
.mcp.jsonis gitignored rather than committed. A checked-in.mcp.jsonwould prompt everyone who clones this repository to enable an unrestricted shell server. That contradicts the consent-and-confirmation posture the rest of Project-Her is built on, so enabling it is left opt-in per user via the example file.The guide draws an explicit boundary against
project-her. The two servers answer different questions —project-heris root-confined and read-only by default with a{"confirm": true}gate on render; Desktop Commander is an unrestricted terminal running under full user permissions, with traffic egressing to a third-party relay in remote mode. The doc states that rather than leaving readers to assume the controls carry over.A section covers what the setup does not apply to. Neither path belongs in an ephemeral web-execution container: local stdio is redundant there, and
remotewould register the throwaway sandbox as the device instead of the user's desktop.Verification
Behavior described in the guide was read off the published package (v0.2.47) rather than recalled —
dist/index.jssubcommand dispatch,dist/npm-scripts/remote.jsflag handling, anddist/remote-device/for the OAuth device-authorization flow (PKCE/S256) and themcp.desktopcommander.apprelay endpoint..mcp.json.exampleparses as valid JSON.Docs-only change; no source or test files touched.
Generated by Claude Code