GoreeCloud Desktop Commander
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
GoreeCloud Desktop Commander
Development-stage, local-first MCP tool server — not a production remote-control service.
GoreeCloud Desktop Commander is a privacy-hardened Rebranded Import of the local open-source DesktopCommanderMCP project, upstream main commit 325a203412612e3be98ea4400d9df59d153068b6. It is not an import or clone of the proprietary Remote Desktop Commander hosted service.
This repository is MIT-licensed with preserved upstream author rights; see LICENSE and NOTICE.md.
Current development scope
The MIT source includes local MCP primitives for file operations, directory search, source editing, command/process handling, and file previews. GoreeCloud modifications disable upstream installation telemetry, regular usage telemetry, persisted raw tool-call argument/output history, upstream background feature-flag polling, marketing onboarding and automatic browser download at startup. The inherited hosted remote mode is disabled: the local executable refuses a remote connection.
Local MCP requests now have an additional development safety gate: filesystem reads are scoped to the working directory by default; configuration/file writes, terminal/process tools and URL reads require explicit operator environment opt-in. A fake or forwarded remote tool marker is always refused. This is a policy guard, not an operating-system sandbox. Read SECURITY.md for configuration and limitations.
This is not an independently self-hosted remote agent/broker. No production-grade authentication, authorization, secured remote relay, native Linux application, Android app, deployment, stable release, or MIPS integration is established. Inherited remote-agent source is not a supported GoreeCloud service and is excluded from the distributed build. The public npm build does not include its upstream hosted-relay client or direct Supabase/MQTT dependencies.
Related MCP server: Local-MCP-Bridge
Local development
Requirements: Node.js 22.12+ and npm on a device you own or are authorized to control.
Clone https://github.com/GoreeCloud/desktop-commander and enter the project directory.
Run npm ci --ignore-scripts --no-audit --no-fund.
Run npm test to compile and execute focused privacy, safety-gate and isolated MCP protocol checks.
Configure a trusted local stdio MCP client to launch node /absolute/path/to/desktop-commander/dist/index.js --no-onboarding.
Commands, filesystem permissions, file conversion and running processes inherit the user account's privileges. Never install as root, connect to untrusted AI agents, or expose an MCP endpoint publicly without independently reviewed security controls. A client may request network access via its commands, so the telemetry shutoff is not a universal network block.
This baseline is for local use and testing; no container deployment is claimed. Evaluate installed GoreeCloud Containers first if a suitable deployable service is later developed.
Status, privacy and security
PRIVACY.md — privacy boundaries and limitations.
SECURITY.md — high-risk command access and reporting.
docs/SECURITY-EXCEPTIONS.md — latest dependency audit and outstanding security acceptance gates.
docs/FEATURES.md — implemented vs planned capability.
docs/ROADMAP.md — next technical steps.
docs/OBJECTIVES.md — requirements and acceptance.
NOTICE.md — full upstream provenance and licensing limitations.
No verified stable, public service, self-hosted relay or device deployment. The inherited unused release, MQTT fixture and coverage toolchains are not shipped as active npm scripts. The supported local development checks are npm test and the CI audits; broader inherited tests and all third-party source still require further review. This is not endorsed by or affiliated with the original upstream parties.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Use a person's computer after they approve it there: files, Terminal, browser, local MCP.
Use a person's computer after they approve it there: files, Terminal, browser, local MCP.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely access local development capabilities such as files, Git, processes, browser control, Windows automation, WSL, and observability through MCP on Windows and macOS.MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to securely access explicitly authorized local project files and run approved development commands with bounded execution and audit logging.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to securely inspect, search, edit, build, and test explicitly authorized local development projects over MCP, with sandboxed filesystem access and sensitive-file protection.2AGPL 3.0
- AlicenseDqualityCmaintenanceEnables controlled local developer operations including file and process management, shell execution, SSH, WSL, Docker, Git, browser and desktop automation, media processing, and asynchronous jobs through MCP.146MIT