Skip to main content
mcpSource-backed
Desktop Commander logo

Desktop Commander MCP Server

Local MCP server that gives AI assistants terminal control, process management, filesystem operations, search, diff editing, and document handling for desktop automation and development workflows.

by wonderwhy-er · submitted by oktofeesh1·added 2026-06-05·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/wonderwhy-er/DesktopCommanderMCP, https://desktopcommander.app/
Brand
Desktop Commander
Brand domain
desktopcommander.app
Brand asset source
brandfetch
Safety notes
Desktop Commander can run shell commands, stream process output, start and stop processes, read and write files, edit documents, search directories, and change local configuration., The project's security policy describes built-in restrictions as guardrails rather than hardened security boundaries., Directory restrictions and command blocklists may be bypassed through terminal access, symlinks, absolute paths, or command substitution., Use Docker with selective folder mounts when stronger isolation is required., Review file edits, command execution, process termination, and document rewrites before letting an agent act on important systems.
Privacy notes
Local files, terminal output, environment-derived paths, process listings, command arguments, audit logs, spreadsheets, PDFs, DOCX files, and source code may be exposed to the MCP client and model., Tool logs can contain secrets, customer data, credentials, private repository paths, database output, and internal documents., If using remote AI clients or the project's remote MCP option, review where prompts, tool calls, and file content are transmitted and retained.
Author
wonderwhy-er
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup.

0/4 ready
Install & runtime2General210 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.

4 areas
  • SafetyLocal filesDesktop Commander can run shell commands, stream process output, start and stop processes, read and write files, edit documents, search directories, and change local configuration.
  • SafetyGeneralThe project's security policy describes built-in restrictions as guardrails rather than hardened security boundaries.
  • SafetyLocal filesDirectory restrictions and command blocklists may be bypassed through terminal access, symlinks, absolute paths, or command substitution.
  • SafetyLocal filesUse Docker with selective folder mounts when stronger isolation is required.
  • SafetyLocal filesReview file edits, command execution, process termination, and document rewrites before letting an agent act on important systems.
  • PrivacyLocal filesLocal files, terminal output, environment-derived paths, process listings, command arguments, audit logs, spreadsheets, PDFs, DOCX files, and source code may be exposed to the MCP client and model.
  • PrivacyCredentials & tokensTool logs can contain secrets, customer data, credentials, private repository paths, database output, and internal documents.
  • PrivacyNetwork accessIf using remote AI clients or the project's remote MCP option, review where prompts, tool calls, and file content are transmitted and retained.

Safety notes

  • Desktop Commander can run shell commands, stream process output, start and stop processes, read and write files, edit documents, search directories, and change local configuration.
  • The project's security policy describes built-in restrictions as guardrails rather than hardened security boundaries.
  • Directory restrictions and command blocklists may be bypassed through terminal access, symlinks, absolute paths, or command substitution.
  • Use Docker with selective folder mounts when stronger isolation is required.
  • Review file edits, command execution, process termination, and document rewrites before letting an agent act on important systems.

Privacy notes

  • Local files, terminal output, environment-derived paths, process listings, command arguments, audit logs, spreadsheets, PDFs, DOCX files, and source code may be exposed to the MCP client and model.
  • Tool logs can contain secrets, customer data, credentials, private repository paths, database output, and internal documents.
  • If using remote AI clients or the project's remote MCP option, review where prompts, tool calls, and file content are transmitted and retained.

Prerequisites

  • Node.js for the npx installation path, or Docker for the isolated installation path.
  • Claude Desktop or another MCP client that can launch local stdio servers.
  • Clear list of directories, commands, and long-running processes an assistant may access.
  • Backups or version control for files the agent may edit.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": ["-y", "@wonderwhy-er/desktop-commander@latest"]
    }
  }
}

About this resource

Content

Desktop Commander MCP gives AI assistants local terminal, filesystem, process, search, and document-editing capabilities. It builds on MCP filesystem concepts and adds process control, command streaming, recursive search, diff editing, document support, configuration management, audit logging, and optional Docker isolation.

The project is useful when a user wants Claude Desktop or another MCP client to work with local code, text files, spreadsheets, PDFs, DOCX files, and long running development processes from one chat workflow.

Source Review

These sources were reviewed on 2026-06-05. Prefer the live repository for current setup options, Docker guidance, security notes, supported file formats, and command behavior.

Features

  • Terminal command execution with streaming output, timeouts, and background process support.
  • Process listing, process termination, and long-running command session management.
  • Filesystem read, write, move, directory listing, metadata, recursive search, and diff-style editing tools.
  • Excel, PDF, and DOCX read/edit workflows described by the project.
  • In-memory execution for Python, Node.js, and R snippets.
  • Audit logging and configuration management.
  • Docker installation path for stronger isolation and selective folder mounts.

Installation

For the Claude Desktop npx setup path:

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

For manual MCP configuration:

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

Use the Docker setup documented in the README when you need stronger isolation or want to restrict which host folders are mounted into the tool environment.

Use Cases

  • Let an assistant search, inspect, and edit a local repository.
  • Stream and monitor development servers, test commands, or database shells.
  • Convert rough instructions into file edits while preserving a reviewable diff.
  • Read and update local spreadsheets, PDFs, or DOCX files from a chat workflow.
  • Run controlled local automation tasks with audit logs.

Safety and Privacy

Desktop Commander is a high-trust local automation server. Treat it like giving an agent shell and filesystem access. Keep important work under version control, limit mounted directories, prefer Docker for sensitive environments, and review commands and file edits before they affect production systems or private data.

Audit logs and tool outputs may contain sensitive local data. Protect or rotate logs when working with credentials, customer data, internal documents, or private repositories.

Duplicate Check

No wonderwhy-er/DesktopCommanderMCP entry or source URL was found in content/mcp. This entry is separate from the reference filesystem MCP server and other editor-specific local automation tools.

Source citations

Add this badge to your README

Show that Desktop Commander MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/desktop-commander-mcp-server.svg)](https://heyclau.de/entry/mcp/desktop-commander-mcp-server)

How it compares

Desktop Commander MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field

Local MCP server that gives AI assistants terminal control, process management, filesystem operations, search, diff editing, and document handling for desktop automation and development workflows.

Open dossier

Browser automation MCP server and Chrome extension that lets AI applications control a connected tab in the user's existing browser profile.

Open dossier

Chrome extension-based MCP server that exposes an existing Chrome browser profile to AI assistants for tab management, page content, screenshots, interaction, history, bookmarks, and network inspection.

Open dossier

Configure MCP servers in the Claude Desktop app by editing claude_desktop_config.json. Grounded walkthrough covering config file locations, the mcpServers JSON structure, the filesystem server, and how to verify and troubleshoot the connection.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustDiffersPackage not verifiedPackage not verifiedPackage not verifiedPackage verified
Source provenanceDiffersSource-backedSource-backedSource-backedNo submission link
SubmitterDiffersoktofeesh1oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandDesktop Commander logoDesktop CommanderBrowserMCP logoBrowserMCPAnthropic logoAnthropic
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedFirst-party
Authorwonderwhy-erBrowserMCPhangwinJSONbored
Added2026-06-052026-06-052026-06-052025-10-27
Platforms
Harness
Source repo
Safety notesDesktop Commander can run shell commands, stream process output, start and stop processes, read and write files, edit documents, search directories, and change local configuration. The project's security policy describes built-in restrictions as guardrails rather than hardened security boundaries. Directory restrictions and command blocklists may be bypassed through terminal access, symlinks, absolute paths, or command substitution. Use Docker with selective folder mounts when stronger isolation is required. Review file edits, command execution, process termination, and document rewrites before letting an agent act on important systems.BrowserMCP can navigate pages, click controls, type text, submit forms, capture screenshots, inspect accessibility snapshots, read console logs, and automate the connected tab. Because it uses the user's real browser profile, logged-in sessions and account permissions may be available to the agent. Require human approval before purchases, messages, account changes, destructive actions, or actions that violate a site's terms. Use a test profile or non-production account for end-to-end testing and repetitive automation.This server controls the user's existing Chrome browser profile and can reuse logged-in sessions. Tools can navigate pages, click elements, fill forms, inspect tabs, capture screenshots, inspect network traffic, read history, manage bookmarks, and inject scripts. Use a dedicated browser profile for agent work and avoid sensitive accounts unless the workflow explicitly requires them. Do not allow agents to submit forms, make purchases, change account settings, or perform irreversible actions without human approval. The project describes itself as early-stage and under active development; test carefully before relying on it for critical workflows.Local MCP servers run as processes on your machine with your user account's privileges, so they can perform any file or system operation you can. Only add servers you trust, and restrict filesystem server paths to the minimum directories the workflow needs. Each Claude Desktop tool call (file write, delete, move) requires your explicit approval before it executes; review every request before approving.
Privacy notesLocal files, terminal output, environment-derived paths, process listings, command arguments, audit logs, spreadsheets, PDFs, DOCX files, and source code may be exposed to the MCP client and model. Tool logs can contain secrets, customer data, credentials, private repository paths, database output, and internal documents. If using remote AI clients or the project's remote MCP option, review where prompts, tool calls, and file content are transmitted and retained.Connected tab content, screenshots, form fields, console logs, and page state may be exposed to the MCP client and model. Logged-in pages can contain personal data, customer information, credentials, tokens, internal URLs, or private documents. Although the project describes local automation, prompts and tool results still flow through the chosen AI application and model provider.Open tabs, page content, screenshots, browsing history, bookmarks, cookies/session-derived page state, and network request metadata may be exposed to the MCP client and model. Screenshots and network responses can contain credentials, personal data, customer data, tokens, and private documents. Browser automation prompts may reveal personal browsing habits, internal applications, and authenticated service access.Configured servers receive the prompts, file contents, and directory data needed to run their tools, and may store credentials (API keys, tokens) passed through the env block. The claude_desktop_config.json file holds server commands, file paths, and environment-variable names; keep it private and do not commit it to public repositories.
Prerequisites
  • Node.js for the npx installation path, or Docker for the isolated installation path.
  • Claude Desktop or another MCP client that can launch local stdio servers.
  • Clear list of directories, commands, and long-running processes an assistant may access.
  • Backups or version control for files the agent may edit.
  • Node.js installed for the MCP server.
  • Chrome or compatible Chromium browser.
  • BrowserMCP extension installed from the project site.
  • MCP client such as Claude, Cursor, VS Code, Windsurf, or another compatible host.
  • Node.js 20 or newer and npm or pnpm.
  • Chrome or Chromium browser.
  • Latest Chrome MCP extension release from the project repository.
  • Globally installed mcp-chrome-bridge package.
  • Claude Desktop installed and running (macOS, Windows, or Linux)
  • Basic JSON knowledge - understand JSON syntax, objects, arrays, and key-value pairs
  • Text editor with JSON syntax highlighting (VS Code, Sublime Text, or similar)
  • Node.js 18+ installed for running npx commands and MCP server packages
Install
npx @wonderwhy-er/desktop-commander@latest setup
npx @browsermcp/mcp@latest
npm install -g mcp-chrome-bridge
node --version
Config
{
  "mcpServers": {
    "desktop-commander": {
      "command": "npx",
      "args": ["-y", "@wonderwhy-er/desktop-commander@latest"]
    }
  }
}
{
  "mcpServers": {
    "browsermcp": {
      "command": "npx",
      "args": ["@browsermcp/mcp@latest"]
    }
  }
}
{
  "mcpServers": {
    "chrome-mcp-stdio": {
      "command": "node",
      "args": ["/ABSOLUTE_PATH_TO/mcp-server-stdio.js"]
    }
  }
}
Edit via Settings > Developer > Edit Config, then restart Claude Desktop:
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/Desktop"
      ]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.