Desktop Commander

Desktop Commander gives an AI assistant control of the local machine: terminal command execution with long-running process management, full filesystem operations including search and document formats (Excel, PDF, DOCX), and code editing through edit_block search-and-replace operations. The README notes it is built on top of the reference MCP Filesystem Server. It runs locally over stdio via npx -y @wonderwhy-er/desktop-commander@latest, under the local user's OS permissions with no MCP-level authentication.

Two operational disclosures from the project's own docs are worth knowing. First, security: the README describes its guardrails as "not a sandbox" and states that directory restrictions and command blocking "can be bypassed through various methods including symlinks, command substitution, and absolute paths or code execution"; Docker is offered as the isolation route. Second, telemetry: PRIVACY.md documents opt-out collection, enabled by default, of pseudonymous usage data via Google Analytics 4, with file paths, contents, command arguments, and usernames explicitly excluded.

The publisher began as individual developer Eduards Ruzga (GitHub wonderwhy-er; the project was previously named ClaudeComputerCommander) and has since incorporated as Desktop Commander SIA in Riga, per the product site's own structured data. A separate hosted Remote MCP gateway at mcp.desktopcommander.app, with OAuth, exists for web clients; it is a distinct service from the npm package this record covers.

No surface names a supported MCP specification revision for the npm package; the @modelcontextprotocol/sdk ^1.9.0 dependency is not evidence of revision support. spec_status is therefore unknown. Registry version 0.2.47 corresponds to a git tag with no published release notes; the latest release with notes is v0.2.44 (2026-07-09).