This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities
6.6k
Stars
781
Forks
149
Open issues
30
Contributors
AI Analysis
Desktop Commander MCP is an AI-powered terminal and file management tool that integrates with Claude and other AI models via the Model Context Protocol, enabling AI agents to execute terminal commands, search files, and edit code. It serves developers and AI enthusiasts who want to automate development workflows and code generation tasks through conversational AI, with best fit for users of Claude Desktop or compatible MCP clients seeking terminal automation capabilities.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
MCP server giving Claude terminal access, file ops, and diff editing for local development automation
Desktop Commander MCP is an open-source Model Context Protocol server that bridges AI assistants (primarily Claude Desktop) with a user's local machine: it grants terminal command execution, full filesystem CRUD, code search/replace, process management, and format-specific support for Excel, PDF, and DOCX files. It targets developers and power users who want AI-driven automation on their own hardware without burning API tokens. A companion desktop app extends support to GPT-4 and Gemini. With 6,400+ stars, weekly npm downloads tracked via badge, and a Discord community, it has visible real-world traction in the MCP ecosystem.
Created in early December 2024, shortly after Anthropic published the Model Context Protocol spec. It grew quickly by being one of the first practical local-machine MCP servers, building on the official MCP Filesystem Server and adding terminal control on top.
Growth was primarily driven by the explosion of interest in MCP as a standard for AI-tool integration in late 2024 and 2025. Being an early, well-documented entry with a clear value proposition (full local machine control for Claude) and active iteration — including a desktop app, remote MCP support, and format expansions — kept momentum going. 205 stars in 7 days as of July 2026 signals continued organic discovery.
npm weekly download badge is visible (exact numbers not captured in metadata but badge presence implies meaningful download volume). Listed on Smithery, Glama.ai, and Archestra.ai MCP catalogs. AgentAudit verified badge present. Discord community exists. Testimonials section in README suggests user feedback collection. Real-world adoption appears genuine but scale beyond individual developer use is unverified.
Appears to be a TypeScript Node.js server implementing the MCP protocol. Likely wraps child_process for terminal execution and extends the official MCP Filesystem Server with additional capabilities. Session management for long-running processes suggests an event-loop or stream-based approach. The companion desktop app appears to be a separate distribution. Docker isolation option suggests the core server is stateless enough to containerize.
not documented in README
Last push was 2026-07-08, one day before evaluation date — highly active. The README references a roadmap, multiple installation options with auto-update support, and a SECURITY.md, indicating structured maintenance. Changelogs and versioned npm releases imply disciplined release cadence.
ADOPT IF: you use Claude Desktop or another MCP-compatible client and want broad local machine automation — terminal, files, processes, and office formats — without setting up bespoke integrations. AVOID IF: you need enterprise-grade sandboxing by default, work in regulated environments where AI-driven shell access raises compliance concerns, or rely on non-MCP AI toolchains. MONITOR IF: you're interested in the companion desktop app's multi-model support maturing, or if your workflow would benefit from remote MCP access once that feature stabilizes.
Independent dimensions
Mainstream potential
6/10
Technical importance
7/10
Adoption evidence
6/10
- Granting an AI assistant unrestricted terminal and filesystem access is a meaningful security surface — the command blocklist and symlink protections exist but a misconfigured or prompt-injected session could cause serious local damage.
- Tight coupling to the MCP protocol means any breaking changes in Anthropic's MCP spec could require rapid updates; the project has kept pace so far but dependency on a third-party standard is a structural risk.
- The companion desktop app introduces a separate codebase and release surface; if maintainer bandwidth is split, one product may lag behind the other.
- Adoption appears concentrated among individual developers and hobbyists; enterprise or team use cases involving shared machines or multi-user environments are not addressed in the README.
- Single-maintainer project risk: no evidence of a broader core team, making bus-factor a concern despite the currently high activity level.
Likely to remain a leading reference implementation for local-machine MCP control as the protocol matures, with the desktop app potentially broadening its audience beyond Claude users. Growth may plateau if AI editors absorb similar capabilities natively.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://desktopcommander.app/
- Language
- TypeScript
- License
- MIT
- Last updated
- 17h ago
- Created
- 19mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
[Security] Command Blocklist Bypass via Newline Injection in start_process — Unfixed Since April 2026 (Issue #422)
[Security] Command Blocklist Bypass via Shell Variable Expansion ${} in start_process — New Variant
edit_block silently truncates file to pre-edit byte length when replacement grows the file
interact_with_process bypasses blockedCommands — missing validateCommand() call in interactWithProcess()
[Security] interact_with_process bypasses blockedCommands - new variant of known limitation
Top contributors
Similar repos
arabold/docs-mcp-server
Grounded Docs is an MCP server that indexes and queries documentation from...
appcypher/awesome-mcp-servers
This is a curated directory of Model Context Protocol (MCP) servers that enable...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
6.6k | +355 | TypeScript | 8/10 | 17h ago |
|
|
2.3k | — | TypeScript | 7/10 | 1w ago |
|
|
1.5k | — | TypeScript | 8/10 | 1mo ago |
|
|
1.8k | — | TypeScript | 8/10 | 3w ago |
|
|
5.7k | — | — | 7/10 | 2mo ago |
|
|
10.3k | — | TypeScript | 8/10 | 13h ago |
mcp-use is a framework for building MCP-connected agents programmatically, not a ready-to-use local machine server. Different abstraction layer — they are complementary rather than direct competitors.
Desktop Commander explicitly builds on top of the official server and extends it. The official server handles basic file I/O; Desktop Commander adds terminal execution, process control, diff editing, and format support. More feature-complete but also more surface area for security risk.
Focused on Gemini model integration rather than local machine control. Serves a different primary use case and target model, though both live in the MCP ecosystem.
Desktop Commander's README explicitly positions itself against AI editors, arguing it avoids per-token API costs by leveraging existing Claude subscriptions. Trade-off: no IDE integration, no GUI diff review, but broader OS-level access.
A curated list rather than a functional tool. Desktop Commander is likely listed there, meaning the list aggregates demand that individual servers like this one serve.