Desktop Commander MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Desktop Commander MCPsearch for 'FIXME' in the src folder"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
๐ฅ๏ธ Desktop Commander MCP
Portable, general-purpose filesystem + terminal tools for MCP clients
Search files ยท edit documents ยท run commands ยท manage processes ยท inspect the local workspace
English ยท ็ฎไฝไธญๆ
A community-maintained portable adaptation of Desktop Commander MCP.
It is designed for standard stdio-compatible MCP clients and does not depend on any vendor-specific deployment platform.
โจ Highlights
Capability | What it gives your AI client |
๐ Filesystem | Read, write, move, list, search, and inspect files and directories |
๐ Fast search | Recursive content search powered by ripgrep |
๐ป Terminal | Run shell commands, stream output, and handle long-running processes |
โ๏ธ Process control | List, inspect, and terminate processes |
๐ Editing | Targeted text replacement and larger file rewrites |
๐ Documents | Excel, PDF, DOCX, Markdown, text, and binary-aware file handling |
๐งฐ Configuration | Runtime configuration plus a conservative default command blocklist |
๐ Cross-platform | Windows, Linux, and macOS source installs with runtime ripgrep resolution |
Related MCP server: Desktop Commander MCP
๐ Quick start
1. Clone
git clone https://github.com/luffy666code/desktop-commander-mcp.git
cd desktop-commander-mcp2. Install and build
npm install
npm run buildRequirements: Node.js 18+ and npm.
3. Verify the search engine
npm run verify:rg4. Add it to your MCP client
Use the standard stdio configuration pattern:
{
"mcpServers": {
"desktop-commander": {
"command": "node",
"args": ["/absolute/path/to/desktop-commander-mcp/dist/index.js"]
}
}
}Replace the path with the real absolute path on your machine. See Client setup for Windows path examples and Inspector usage.
๐งญ How it works
MCP client
โ
โ stdio / MCP requests
โผ
dist/index.js
โ
โผ
server + tool handlers
โ
โโโ filesystem operations
โโโ terminal / process manager
โโโ document utilities
โโโ search manager
โ
โผ
ripgrepThe ripgrep resolver first checks the platform-correct binary in @vscode/ripgrep, then falls back to the package export, the system PATH, and common installation locations. On Unix-like systems it also verifies executable permission.
๐ Safety defaults
config.json ships with a conservative blocklist for destructive or privilege-escalating commands such as format, mkfs, fdisk, dd, sudo, and user-management commands.
{
"blockedCommands": [
"format", "mount", "umount", "mkfs", "fdisk", "dd",
"sudo", "su", "passwd", "adduser", "useradd", "usermod", "groupadd"
]
}This is a guardrail, not a sandbox. Review SECURITY.md before using command execution against important data or production machines.
๐ ๏ธ Development
# TypeScript watch mode
npm run watch
# Run from TypeScript during development
npm run dev
# Compile
npm run build
# Start compiled server
npm start
# Open MCP Inspector
npm run inspectorProject layout
src/
โโโ index.ts # process entry point
โโโ server.ts # MCP server and tool registration
โโโ handlers/ # request handlers
โโโ tools/ # filesystem, edit, process, PDF and other tools
โโโ search-manager.ts # search orchestration
โโโ terminal-manager.ts # command/session management
โโโ utils/
โโโ ripgrep-resolver.ts # cross-platform ripgrep discovery๐ Portability notes
For normal use, run npm install on the same OS/architecture where the MCP server will run so native dependencies are installed correctly.
The repository also contains an optional Linux x86-64 ripgrep binary under tools/Linux/rg for custom portable packaging workflows. It is not required for ordinary source installs. See tools/README.md.
๐ค Upstream & attribution
This repository is derived from Desktop Commander MCP by Eduard Ruzga and contributors:
Upstream: https://github.com/wonderwhy-er/DesktopCommanderMCP
License: MIT
Portable packaging and ripgrep-resolution adjustments in this fork are maintained separately. Upstream trademarks, services, and release channels are not implied to endorse this fork.
See LICENSE and THIRD_PARTY_NOTICES.md.
๐ License
MIT License. See LICENSE.
Built for developers who want a straightforward, local-first MCP tool server.
This server cannot be deployed
Maintenance
Related MCP Connectors
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Local-first, governed memory and session continuity for AI coding agents. No cloud, no telemetry.
91Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
Shared control plane for AI coding agents โ tasks, memory, decisions, file locks. 12 tools.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to safely perform actions on your computer including file system management, command execution, clipboard access, application launching, and local search with license-based monetization built in.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search, update, and manage files, run terminal commands, and automate workflows on a user's computer.125,805 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to remotely search, update, manage files, and run terminal commands on a desktop environment via Streamable HTTP with OAuth 2.0, supporting ChatGPT and web agent integrations.125,805 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, update, manage files, and run terminal commands on a computer, with remote access via Streamable HTTP and OAuth 2.0 for integration with ChatGPT and web agents.125,805 npmMIT