roymejia2217/jamedesktopcommander

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

0 stars 0 forks Качество 87 Тренд 20MIT

Repository Install

Production-grade MCP orchestration for local desktop automation and development.

Обзор

Production-grade MCP orchestration for local desktop automation and development. JameDesktopCommander (JDC) is an independent fork of wonderwhy-er/DesktopCommanderMCP. The source tree temporarily retains upstream npm and MCP Registry identifiers for compatibility while the fork is under active development. JDC does not publish to upstream-owned namespaces. JameDesktopCommander brings local development, automation, process control, OpenCode orchestration, and desktop interaction into one MCP surface. It remains compatible with the upstream Desktop Commander architecture while adding JDC-specific runtime, security, and governance layers. JameDesktopCommander extends Desktop Commander MCP with production-oriented Windows runtime integration, OpenCode orchestration, semantic Computer Use foundations, OpenAI Secure MCP Tunnel lifecycle management, and enforceable repository governance. Linux remains a planned first-class platform rather than a compatibility afterthought.

README

Показан фрагмент оригинального README. Открыть оригинал.

JameDesktopCommander

Production-grade MCP orchestration for local desktop automation and development.

JameDesktopCommander (JDC) is an independent fork of wonderwhy-er/DesktopCommanderMCP. The source tree temporarily retains upstream npm and MCP Registry identifiers for compatibility while the fork is under active development. JDC does not publish to upstream-owned namespaces.

Background
Install
Usage
Windows Secure MCP Tunnel Lifecycle
Windows UI Bridge Lifecycle
Features
Getting Started
File Preview UI & Markdown Editor
Handling Long-Running Commands
Work in Progress and TODOs
Frequently Asked Questions
Data Collection & Privacy
Maintainers
Contributing
License

JameDesktopCommander brings local development, automation, process control, OpenCode orchestration, and desktop interaction into one MCP surface. It remains compatible with the upstream Desktop Commander architecture while adding JDC-specific runtime, security, and governance layers.

Background

JameDesktopCommander extends Desktop Commander MCP with production-oriented Windows runtime integration, OpenCode orchestration, semantic Computer Use foundations, OpenAI Secure MCP Tunnel lifecycle management, and enforceable repository governance. Linux remains a planned first-class platform rather than a compatibility afterthought.

The project preserves upstream architecture where doing so keeps synchronization practical while deliberately diverging where JDC requires stronger Windows lifecycle, security, testing, or release guarantees. Its intellectual provenance is wonderwhy-er/DesktopCommanderMCP, licensed under MIT.

The intended repository identity is JameDesktopCommander. The inherited npm package @wonderwhy-er/desktop-commander and MCP Registry identifier are transitional metadata only; they belong to upstream and are not publication targets for JDC.

Install

JameDesktopCommander is not yet published to npm or the MCP Registry. For the current development line, install dependencies and build from a checked-out JDC source tree:

npm ci
npm run build
node dist/index.js --help

JDC requires Node.js 22.19.0 or newer. By default, runtime configuration remains in ~/.claude-server-commander. Managed deployments can override only the configuration root with

Открыть полный README на GitHub

Установка

npx -y @wonderwhy-er/desktop-commander@latest

Новичок в MCP? Начните с руководства на mcpskill.org →

Конфигурация

{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": [
        "-y",
        "@wonderwhy-er/desktop-commander@latest"
      ]
    }
  }
}