ClaudeDesktopCommander MCP

MCPAI代理

提供方 未标注

AI代理 stdio · 本地进程 未标注 社区 / 第三方
查看接入方式

全面解析ClaudedesktopcommanderMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,Claudedesktopcommander能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

ClaudeDesktopCommander MCP 属于AI代理类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx install -g desktop-commander-mcp@latest

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
ClaudeDesktopCommander MCP当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

41.7 KB
来自项目仓库与上游目录的原文,未做删改

Desktop Commander MCP

Search, update, manage files and run terminal commands with AI

Work with code and text, run processes, and automate tasks, going far beyond other AI editors - while using host client subscriptions instead of API token costs.

Table of Contents

  • Features
  • How to install
  • Getting Started
  • Usage
  • File Preview UI & Markdown Editor
  • Handling Long-Running Commands
  • Work in Progress and TODOs
  • Sponsors and Supporters
  • Website
  • Media
  • Testimonials
  • Frequently Asked Questions
  • Contributing
  • License

All of your AI development tools in one place.
Desktop Commander puts all dev tools in one chat.
Execute long-running terminal commands on your computer and manage processes through Model Context Protocol (MCP). Built on top of MCP Filesystem Server to provide additional search and replace file editing capabilities.

Features

  • Remote AI Control - Use Desktop Commander from ChatGPT, Claude web, and other AI services via Remote MCP
  • File Preview UI - Visual file previews in Claude Desktop with rendered markdown, inline images, expandable content, built-in markdown editor, and quick "Open in folder" access
  • Enhanced terminal commands with interactive process control
  • Execute code in memory (Python, Node.js, R) without saving files
  • Instant data analysis - just ask to analyze CSV/JSON/Excel files
  • Native Excel file support - Read, write, edit, and search Excel files (.xlsx, .xls, .xlsm) without external tools
  • PDF support - Read PDFs with text extraction, create new PDFs from markdown, modify existing PDFs
  • DOCX support - Read, create, edit, and search Word documents (.docx) with surgical XML editing and markdown-to-DOCX conversion
  • Interact with running processes (SSH, databases, development servers)
  • Execute terminal commands with output streaming
  • Command timeout and background execution support
  • Process management (list and kill processes)
  • Session management for long-running commands
  • Process output pagination - Read terminal output with offset/length controls to prevent context overflow
  • Server configuration management:
  • Get/set configuration values
  • Update multiple settings at once
  • Dynamic configuration changes without server restart
  • Full filesystem operations:
  • Read/write files (text, Excel, PDF, DOCX)
  • Create/list directories
  • Recursive directory listing with configurable depth and context overflow protection for large folders
  • Move files/directories
  • Search files and content (including Excel content)
  • Get file metadata
  • Negative offset file reading: Read from end of files using negative offset values (like Unix tail)
  • Code editing capabilities:
  • Surgical text replacements for small changes
  • Full file rewrites for major changes
  • Multiple file support
  • Pattern-based replacements
  • vscode-ripgrep based recursive code or text search in folders
  • Local tool-call history and audit logs:
  • Tool calls and arguments are recorded locally on the machine running Desktop Commander
  • Recent call history with bounded output previews is available through get_recent_tool_calls
  • Size-based rotation/trimming keeps the active history files bounded
  • Safety guardrails (not a sandbox — see SECURITY.md):
  • Symlink traversal prevention on file operations
  • Command blocklist for accidental execution
  • Docker isolation for complete isolation

How to install

For ChatGPT, Claude web, and other remote clients, see the Remote device launchers. They install Node.js when missing and run Desktop Commander Remote on macOS, Linux, or Windows.

Install in Claude Desktop

Desktop Commander offers multiple installation methods for Claude Desktop.

> 📋 Update & Uninstall Information: Options 1, 2, 3, 4, and 6 have automatic updates. Option 5 requires manual updates. See below for details.

Option 1: Install through npx ⭐ Auto-Updates (Requires Node.js)

Just run this in terminal:```
npx @wonderwhy-er/desktop-commander@latest setup


For debugging mode (allows Node.js inspector connection):```
npx @wonderwhy-er/desktop-commander@latest setup --debug

Command line options during setup:
- --debug: Enable debugging mode for Node.js inspector
- --no-onboarding: Disable onboarding prompts for new users

Restart Claude if running.

✅ Auto-Updates: Yes - automatically updates when you restart Claude
🔄 Manual Update: Run the setup command again
🗑️ Uninstall: Run npx @wonderwhy-er/desktop-commander@latest remove

Option 2: Using bash script installer (macOS) ⭐ Auto-Updates (Installs Node.js if needed)```
curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install.sh | bash

This script handles all dependencies and configuration automatically.

**✅ Auto-Updates:** Yes
**🔄 Manual Update:** Re-run the bash installer command above
**🗑️ Uninstall:** Run `npx @wonderwhy-er/desktop-commander@latest remove`

Option 3: Installing via Smithery ⭐ Auto-Updates (Requires Node.js)

1. **Visit:** https://smithery.ai/server/@wonderwhy-er/desktop-commander
2. **Login to Smithery** if you haven't already
3. **Select your client** (Claude Desktop) on the right side
4. **Install with the provided key** that appears after selecting your client
5. **Restart Claude Desktop**

**✅ Auto-Updates:** Yes - automatically updates when you restart Claude
**🔄 Manual Update:** Visit the Smithery page and reinstall

Option 4: Add to claude_desktop_config manually ⭐ Auto-Updates (Requires Node.js)

Add this entry to your claude_desktop_config.json:

- On Mac: `~/Library/Application Support/Claude/claude_desktop_config.json`
- On Windows: `%APPDATA%\Claude\claude_desktop_config.json`
- On Linux: `~/.config/Claude/claude_desktop_config.json````json
{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": [
        "-y",
        "@wonderwhy-er/desktop-commander@latest"
      ]
    }
  }
}

Restart Claude if running.

✅ Auto-Updates: Yes - automatically updates when you restart Claude
🔄 Manual Update: Run the setup command again
🗑️ Uninstall: Run npx @wonderwhy-er/desktop-commander@latest remove or remove the entry from your claude_desktop_config.json

Option 5: Checkout locally ❌ Manual Updates (Requires Node.js)```bash
git clone https://github.com/wonderwhy-er/DesktopCommanderMCP.git
cd DesktopCommanderMCP
npm run setup

Restart Claude if running.

The setup command will install dependencies, build the server, and configure Claude's desktop app.

**❌ Auto-Updates:** No - requires manual git updates
**🔄 Manual Update:** `cd DesktopCommanderMCP && git pull && npm run setup`
**🗑️ Uninstall:** Run `npx @wonderwhy-er/desktop-commander@latest remove` or remove the cloned directory and MCP server entry from Claude config

Option 6: Docker Installation 🐳 ⭐ Auto-Updates (No Node.js Required)

Perfect for users who want isolation or don't have Node.js installed. Runs in a sandboxed Docker container with a persistent work environment.

**Prerequisites:** Docker Desktop installed **and running**, Claude Desktop app installed.

**macOS/Linux:**```bash
bash <(curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.sh)

Windows PowerShell:```powershell
iex ((New-Object System.Net.WebClient).DownloadString('https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1'))


The installer will check Docker, pull the image, prompt for folder mounting, and configure Claude Desktop.

**Docker persistence:** Your tools, configs, work files, and package caches all survive restarts.

Manual Docker Configuration

**Basic setup (no file access):**```json
{
  "mcpServers": {
    "desktop-commander-in-docker": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "mcp/desktop-commander:latest"]
    }
  }
}

With folder mounting:```json
{
"mcpServers": {
"desktop-commander-in-docker": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-v", "/Users/username/Desktop:/mnt/desktop",
"-v", "/Users/username/Documents:/mnt/documents",
"mcp/desktop-commander:latest"
]
}
}
}


**Advanced folder mounting:**```json
{
  "mcpServers": {
    "desktop-commander-in-docker": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "dc-system:/usr",
        "-v", "dc-home:/root",
        "-v", "dc-workspace:/workspace",
        "-v", "dc-packages:/var",
        "-v", "/Users/username/Projects:/mnt/Projects",
        "-v", "/Users/username/Downloads:/mnt/Downloads",
        "mcp/desktop-commander:latest"
      ]
    }
  }
}

Docker Management Commands

macOS/Linux:```bash

Check status

bash <(curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.sh) --status

Reset all persistent data

bash <(curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.sh) --reset


**Windows PowerShell:**```powershell
# Check status
$script = (New-Object System.Net.WebClient).DownloadString(&#x27;https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1&#x27;); &amp; ([ScriptBlock]::Create(&quot;$script&quot;)) -Status

# Reset all data
$script = (New-Object System.Net.WebClient).DownloadString(&#x27;https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1&#x27;); &amp; ([ScriptBlock]::Create(&quot;$script&quot;)) -Reset

# Show help
$script = (New-Object System.Net.WebClient).DownloadString(&#x27;https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.ps1&#x27;); &amp; ([ScriptBlock]::Create(&quot;$script&quot;)) -Help

Troubleshooting: Reset and reinstall from scratch:```bash
bash <(curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.sh) --reset && bash <(curl -fsSL https://raw.githubusercontent.com/wonderwhy-er/DesktopCommanderMCP/refs/heads/main/install-docker.sh)


**✅ Auto-Updates:** Yes - `latest` tag automatically gets newer versions
**🔄 Manual Update:** `docker pull mcp/desktop-commander:latest` then restart Claude

### Install in Other Clients

Desktop Commander works with any MCP-compatible client. The standard JSON configuration is:```json
{
  &quot;mcpServers&quot;: {
    &quot;desktop-commander&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [&quot;-y&quot;, &quot;@wonderwhy-er/desktop-commander@latest&quot;]
    }
  }
}

Add this to your client's MCP configuration file at the locations below:

Cursor

View MCP Server in Directory

Or add manually to ~/.cursor/mcp.json (global) or .cursor/mcp.json in your project folder (project-specific).

See Cursor MCP docs for more info.

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json. See Windsurf MCP docs for more info.

VS Code / GitHub Copilot

Add to .vscode/mcp.json in your project or VS Code User Settings (JSON). Make sure MCP is enabled under Chat > MCP. Works in Agent mode.

See VS Code MCP docs for more info.

Cline

Configure through the Cline extension settings in VS Code. Open the Cline sidebar, click the MCP Servers icon, and add the JSON configuration above. See Cline MCP docs for more info.

Roo Code

Add to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.

Claude Code```sh
claude mcp add --scope user desktop-commander -- npx -y @wonderwhy-er/desktop-commander@latest


Remove `--scope user` to install for the current project only. See Claude Code MCP docs for more info.

Trae

Use the &quot;Add manually&quot; feature and paste the JSON configuration above. See Trae MCP docs for more info.

Kiro

Navigate to `Kiro` &gt; `MCP Servers`, click `+ Add`, and paste the JSON configuration above. See Kiro MCP docs for more info.

Codex (OpenAI)

Codex uses TOML configuration. Run this command to add Desktop Commander:```sh
codex mcp add desktop-commander -- npx -y @wonderwhy-er/desktop-commander@latest

Or manually add to ~/.codex/config.toml:```toml
[mcp_servers.desktop-commander]
command = "npx"
args = ["-y", "@wonderwhy-er/desktop-commander@latest"]


See Codex MCP docs for more info.

JetBrains (AI Assistant)

In JetBrains IDEs, go to **Settings → Tools → AI Assistant → Model Context Protocol (MCP)**, click `+` Add, select **As JSON**, and paste the JSON configuration above. See JetBrains MCP docs for more info.

Gemini CLI

Add to `~/.gemini/settings.json`:```json
{
  &quot;mcpServers&quot;: {
    &quot;desktop-commander&quot;: {
      &quot;command&quot;: &quot;npx&quot;,
      &quot;args&quot;: [&quot;-y&quot;, &quot;@wonderwhy-er/desktop-commander@latest&quot;]
    }
  }
}

See Gemini CLI docs for more info.

Augment Code

Press Cmd/Ctrl+Shift+P, open the Augment panel, and add a new MCP server named desktop-commander with the JSON configuration above. See Augment Code MCP docs for more info.

Qwen Code

Run this command to add Desktop Commander:```sh
qwen mcp add desktop-commander -- npx -y @wonderwhy-er/desktop-commander@latest


Or add to `.qwen/settings.json` (project) or `~/.qwen/settings.json` (global). See Qwen Code MCP docs for more info.

ChatGPT / Claude Web (Remote MCP)

Use Desktop Commander from **ChatGPT**, **Claude web**, and other AI services while commands still execute on your computer.

Start the Remote Device:```bash
npx @wonderwhy-er/desktop-commander@latest remote

On first run, complete browser authentication, then connect your AI at mcp.desktopcommander.app.

  • Stop the local device temporarily with Ctrl+C
  • See available CLI options with npx @wonderwhy-er/desktop-commander@latest remote --help
  • See Remote MCP setup, logout/revocation, CLI reference, and troubleshooting

Security

  • ✅ The Remote Device only accepts commands while it is running
  • ✅ Commands execute locally under your user permissions
  • ✅ Secure OAuth authentication and encrypted communication channel

Updating & Uninstalling Desktop Commander

Automatic Updates (Options 1, 2, 3, 4 & 6)

Options 1 (npx), Option 2 (bash installer), 3 (Smithery), 4 (manual config), and 6 (Docker) automatically update to the latest version whenever you restart Claude. No manual intervention needed.

Manual Updates (Option 5)

  • Option 5 (local checkout): cd DesktopCommanderMCP &amp;&amp; git pull &amp;&amp; npm run setup

Uninstalling Desktop Commander

🤖 Automatic Uninstallation (Recommended)

The easiest way to completely remove Desktop Commander:```bash
npx @wonderwhy-er/desktop-commander@latest remove


This automatic uninstaller will:
- ✅ Remove Desktop Commander from Claude&#x27;s MCP server configuration
- ✅ Create a backup of your Claude config before making changes
- ✅ Provide guidance for complete package removal
- ✅ Restore from backup if anything goes wrong

#### 🔧 Manual Uninstallation

If the automatic uninstaller doesn&#x27;t work or you prefer manual removal:

##### Remove from Claude Configuration

1. **Locate your Claude Desktop config file:**
  - **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
  - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
  - **Linux:** `~/.config/Claude/claude_desktop_config.json`

2. **Edit the config file:**
  - Open the file in a text editor
  - Find and remove the `&quot;desktop-commander&quot;` entry from the `&quot;mcpServers&quot;` section
  - Save the file

  **Example - Remove this section:**```json
  {
      &quot;desktop-commander&quot;: {
        &quot;command&quot;: &quot;npx&quot;,
        &quot;args&quot;: [&quot;@wonderwhy-er/desktop-commander@latest&quot;]
      }
  }
  ```

Close and restart Claude Desktop to complete the removal.

#### 🆘 Troubleshooting

**If automatic uninstallation fails:**
- Use manual uninstallation as a fallback

**If Claude won&#x27;t start after uninstalling:**
- Restore the backup config file created by the uninstaller
- Or manually fix the JSON syntax in your claude_desktop_config.json

**Need help?**
- Join our Discord community: https://discord.com/invite/kQ27sNnZr7

## Getting Started

Once Desktop Commander is installed and Claude Desktop is restarted, you&#x27;re ready to supercharge your Claude experience!

### 🚀 New User Onboarding

Desktop Commander includes intelligent onboarding to help you discover what&#x27;s possible:

**For New Users:** When you&#x27;re just getting started (fewer than 10 successful commands), Claude will automatically offer helpful getting-started guidance and practical tutorials after you use Desktop Commander successfully.

**Request Help Anytime:** You can ask for onboarding assistance at any time by simply saying:
- *&quot;Help me get started with Desktop Commander&quot;*
- *&quot;Show me Desktop Commander examples&quot;*
- *&quot;What can I do with Desktop Commander?&quot;*

Claude will then show you beginner-friendly tutorials and examples, including:
- 📁 Organizing your Downloads folder automatically
- 📊 Analyzing CSV/Excel files with Python
- ⚙️ Setting up GitHub Actions CI/CD
- 🔍 Exploring and understanding codebases
- 🤖 Running interactive development environments

## Usage

The server provides a comprehensive set of tools organized into several categories:

### Available Tools

| Category | Tool | Description |
|----------|------|-------------|
| **Configuration** | `get_config` | Get the complete server configuration as JSON (includes blockedCommands, defaultShell, allowedDirectories, fileReadLineLimit, fileWriteLineLimit, telemetryEnabled) |
| | `set_config_value` | Set a specific configuration value by key. Available settings:

• `blockedCommands`: Array of shell commands that cannot be executed
• `defaultShell`: Shell to use for commands (e.g., bash, zsh, powershell)
• `allowedDirectories`: Array of filesystem paths the server can access for file operations (⚠️ terminal commands can still access files outside these directories)
• `fileReadLineLimit`: Maximum lines to read at once (default: 1000)
• `fileWriteLineLimit`: Maximum lines to write at once (default: 50)
• `telemetryEnabled`: Enable/disable telemetry (boolean) |
**Terminal** · `start_process` · Start programs with smart detection of when they&#x27;re ready for input
`interact_with_process` · Send commands to running programs and get responses
`read_process_output` · Read output from running processes
`force_terminate` · Force terminate a running terminal session
`list_sessions` · List all active terminal sessions
`list_processes` · List all running processes with detailed information
`kill_process` · Terminate a running process by PID
**Filesystem** · `read_file` · Read contents from local filesystem, URLs, Excel files (.xlsx, .xls, .xlsm), and PDFs with line/page-based pagination
`read_multiple_files` · Read multiple files simultaneously
`write_file` · Write file contents with options for rewrite or append mode. Supports Excel files (JSON 2D array format). For PDFs, use `write_pdf`
`write_pdf` · Create new PDF files from markdown or modify existing PDFs (insert/delete pages). Supports HTML/CSS styling and SVG graphics
`create_directory` · Create a new directory or ensure it exists
`list_directory` · Get detailed recursive listing of files and directories (supports depth parameter, default depth=2)
`move_file` · Move or rename files and directories
`start_search` · Start streaming search for files by name or content patterns (searches text files and Excel content)
`get_more_search_results` · Get paginated results from active search with offset support
`stop_search` · Stop an active search gracefully
`list_searches` · List all active search sessions
`get_file_info` · Retrieve detailed metadata about a file or directory (includes sheet info for Excel files)
**Text Editing** · `edit_block` · Apply targeted text replacements for text files, or range-based cell updates for Excel files
**Analytics** · `get_usage_stats` · Get usage statistics for your own insight
`get_recent_tool_calls` · Get recent tool call history with arguments and outputs for debugging and context recovery
`give_feedback_to_desktop_commander` · Open feedback form in browser to provide feedback to Desktop Commander Team

### Quick Examples

**Data Analysis:**```
&quot;Analyze sales.csv and show top customers&quot; → Claude runs Python code in memory

Remote Access:```
"SSH to my server and check disk space" → Claude maintains SSH session


**Development:**```
&quot;Start Node.js and test this API&quot; → Claude runs interactive Node session

Tool Usage Examples

Search/Replace Block Format:```
filepath.ext
<<<<<<< SEARCH
content to find
=======
new content
>>>>>>> REPLACE


Example:```
src/main.js
&lt;&lt;&lt;&lt;&lt;&lt;&lt; SEARCH
console.log(&quot;old message&quot;);
=======
console.log(&quot;new message&quot;);
&gt;&gt;&gt;&gt;&gt;&gt;&gt; REPLACE

Enhanced Edit Block Features

The edit_block tool includes several enhancements for better reliability:

  1. Improved Prompting: Tool descriptions now emphasize making multiple small, focused edits rather than one large change
  2. Fuzzy Search Fallback: When exact matches fail, it performs fuzzy search and provides detailed feedback
  3. Character-level Diffs: Shows exactly what's different using {-removed-}{+added+} format
  4. Multiple Occurrence Support: Can replace multiple instances with expected_replacements parameter
  5. Comprehensive Logging: All fuzzy searches are logged for analysis and debugging

When a search fails, you'll see detailed information about the closest match found, including similarity percentage, execution time, and character differences. All these details are automatically logged for later analysis using the fuzzy search log tools.

Docker Support

🐳 Isolated Environment Usage

Desktop Commander can be run in Docker containers for complete isolation from your host system, providing zero risk to your computer. This is perfect for testing, development, or when you want complete sandboxing.

Installation Instructions

  1. Install Docker for Windows/Mac
    - Download and install Docker Desktop from docker.com

  2. Get Desktop Commander Docker Configuration
    - Visit: https://hub.docker.com/mcp/server/desktop-commander/manual
    - Option A: Use the provided terminal command for automated setup
    - Option B: Click "Standalone" to get the config JSON and add it manually to your Claude Desktop config

  3. Mount Your Machine Folders (Coming Soon)
    - Instructions on how to mount your local directories into the Docker container will be provided soon
    - This will allow you to work with your files while maintaining complete isolation

Benefits of Docker Usage

  • Complete isolation from your host system
  • Consistent environment across different machines
  • Easy cleanup - just remove the container when done
  • Perfect for testing new features or configurations

URL Support

  • read_file can now fetch content from both local files and URLs
  • Example: read_file with isUrl: true parameter to read from web resources
  • Handles both text and image content from remote sources
  • Images (local or from URLs) are displayed visually in Claude's interface, not as text
  • Claude can see and analyze the actual image content
  • Default 30-second timeout for URL requests

File Preview UI & Markdown Editor

Desktop Commander includes a rich file preview widget in Claude Desktop that renders files visually as AI works with them.

Supported file types

  • Markdown — rendered preview with a built-in editor
  • Images — inline display (PNG, JPEG, GIF, WebP, etc.)
  • Code files — syntax-highlighted source view
  • HTML — rendered preview with toggle to source view
  • Directories — interactive tree with expand/collapse and lazy loading
  • PDF, Excel, DOCX — native content extraction and display

Markdown Editor

When viewing a .md file in Claude Desktop, you can edit it directly inside the preview panel — no need to open a separate app.

How to use:
1. Ask Claude to read or create a markdown file
2. Expand the file preview to fullscreen using the ⤢ Expand button
3. The editor activates automatically in fullscreen mode
4. Edit your content with a live preview toggle, copy, undo, and save controls
5. Changes are saved back to disk; collapse to return to inline view

Editor features:
- Live edit / preview toggle — switch between raw markdown and rendered output
- Auto-save to disk with save status indicator
- Undo support to revert unsaved changes
- Copy button to grab the full markdown source
- Open in editor — launch your default markdown app directly from the panel
- Partial-file awareness — loads and merges surrounding lines when the file was only partially read
- Text selection context — select text in preview mode and the AI can reference your selection

Directory Browser

When Claude runs list_directory, the result opens as an interactive file tree inside the preview panel — not just raw text output.

Features:
- Expandable tree — folders expand and collapse on click; top-level contents shown immediately
- Lazy loading — subfolders load on demand to keep the initial view fast
- Large directory handling — directories with many items show a ⚠ click to load all button instead of overwhelming the view
- Open in Finder/Explorer — each folder has a quick-open button to reveal it in your file manager
- Click to preview — clicking any file in the tree opens it in the file preview panel directly
- Back navigation — after opening a file from the tree, a ← Back button returns you to the directory view

Other preview features

  • Expand / collapse — toggle between compact summary row and full panel
  • Open in folder — reveal the file in Finder/Explorer with one click
  • Load more lines — incrementally load content above or below a partial read window
  • Text selection — highlight text in any preview; the AI can see and reference your selection

Fuzzy Search Log Analysis (npm scripts)

The fuzzy search logging system includes convenient npm scripts for analyzing logs outside of the MCP environment:```bash

View recent fuzzy search logs

npm run logs:view -- --count 20

Analyze patterns and performance

npm run logs:analyze -- --threshold 0.8

Export logs to CSV or JSON

npm run logs:export -- --format json --output analysis.json

Clear all logs (with confirmation)

npm run logs:clear
```

For detailed documentation on these scripts, see scripts/README.md.

Fuzzy Search Logs

Desktop Commander includes comprehensive logging for fuzzy search operations in the edit_block tool. When an exact match isn't found, the system performs a fuzzy search and logs detailed information for analysis.

What Gets Logged

Every fuzzy search operation logs:
- Search and found text: The text you're looking for vs. what was found
- Similarity score: How close the match is (0-100%)
- Execution time: How long the search took
- Character differences: Detailed diff showing exactly what's different
- File metadata: Extension, search/found text lengths
- Character codes: Specific character codes causing differences

Log Location

Logs are automatically saved to:
- macOS/Linux: ~/.claude-server-commander-logs/fuzzy-search.log
- Windows: %USERPROFILE%\.claude-server-commander-logs\fuzzy-search.log

What You'll Learn

The fuzzy search logs help you understand:
1. Why exact matches fail: Common issues like whitespace differences, line endings, or character encoding
2. Performance patterns: How search complexity affects execution time
3. File type issues: Which file extensions commonly have matching problems
4. Character encoding problems: Specific character codes that cause diffs

Local Tool History and Audit Logs

Desktop Commander keeps tool-call records locally on the machine running the MCP server. These local files are separate from optional telemetry and are not a server-side historical audit log.

claude_tool_call.log — local argument log

Every tool call handled by the local MCP server is appended as a text line containing an ISO timestamp, the tool name, and the JSON-serialized arguments. Arguments are not redacted or sanitized before being written to this local file, so it may contain command text, file paths, or other sensitive values passed to tools. Tool outputs are not written to this file.

The active file rotates when it reaches 10 MB. The previous file is renamed using a timestamp, for example claude_tool_call_2026-09-07_14-32-10.log, and a new claude_tool_call.log is created. Rotated files are not automatically deleted by the logger.

Locations:
- macOS/Linux: ~/.claude-server-commander/claude_tool_call.log
- Windows: %USERPROFILE%\.claude-server-commander\claude_tool_call.log

tool-history.jsonl — recent tool-call history

Desktop Commander also keeps a JSON Lines history used by get_recent_tool_calls. Each record contains the timestamp, tool name, arguments, duration, and the returned result. This history is loaded from disk on startup, so recent history can survive an MCP server restart.

To keep this history bounded:
- At most the most recent 1,000 calls are kept in memory.
- Stored output is capped at 4 KiB per record; larger outputs are replaced with an omission marker.
- The on-disk file is trimmed when it grows beyond 5 MiB, keeping roughly the newest 4 MiB.
- On startup, a history with more than 2,000 records is rewritten to the most recent 1,000 records.
- get_recent_tool_calls and track_ui_event are excluded from this JSONL history.

Locations:
- macOS/Linux: ~/.claude-server-commander/tool-history.jsonl
- Windows: %USERPROFILE%\.claude-server-commander\tool-history.jsonl

Remote calls and server-side retention

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
ClaudeDesktopCommander MCP 怎么安装?

在客户端按下面的安装命令接入:npx install -g desktop-commander-mcp@latest。装完在客户端配置里引用同一个包或端点。

ClaudeDesktopCommander MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

ClaudeDesktopCommander MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

ClaudeDesktopCommander MCP 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

ClaudeDesktopCommander MCP 能提供哪些能力?

资料显示能力标签包括 JavaScript、AI自动化、文件管理。具体工具清单以官方文档为准。

ClaudeDesktopCommander MCP 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

ClaudeDesktopCommander MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。