Desktop Commander plugin: 10,000-star popular MCP, give Claude a double terminal and a hand to change filesDesktop Commander 插件：一万星热门 MCP，给 Claude 一双管终端和改文件的手

The most annoying thing about using the AI programming assistant is moving it back and forth: let the AI write a command, you copy it to the terminal, run it, and then glue the output back, and it will be gone in a few minutes after one round.

Desktop Commander hands the terminal and file system directly to AI: it can start the process, read the output, search the file, and accurately edit the code by diff, all without needing you as a transit station.

It is a standard MCP server. Claude Desktop, Claude Code and other clients that support MCP can access it. GitHub has won tens of thousands of stars, which is one of the most popular choices in its class.

Terminal control: execute arbitrary command line, start permanent process, read output by line, support timeout and process management.

File ability: Recursively search the file content, blur the file name, read the edited text file, and accurately modify it in diff format to avoid errors in rewriting the entire file.

Accessibility: Test the code running unit, manage Git operations, compress and extract files, and basically cover all the high-frequency actions of daily development.

Option 1 (recommended): Add an npx command to the configuration file of Claude Desktop, point to @ wonderwhy-er/desktop-commander, and restart the client.

Option 2 (offline): Download the official npm installation package (tgz format, only 1.70 MB) included in this article, and use the npx local path to access after unzipping, which is suitable for environments with inconvenient networks.

After plugging in, say directly in the dialog, "Help me run the npm test and fix the failed use case", the AI will execute the command, read the output, change the code, and re-validate it.

The download button provides the npm official repository @ wonderwhy-er/desktop-commander version 0.3.0 installation package (tgz format, 1.70 MB), which can be installed offline by npm install.

It is recommended to use with version management: lock the version number in the MCP configuration, and verify it in the test project before upgrading to avoid changes in tool behavior from affecting the existing workflow.

This article is compiled from public sources and ships with the matching resource. Product features and pricing are subject to the official page. Resources are for learning and exchange only — please respect the original license.