Skip to main content
plugin

desktop-commander — Claude Code plugin: what it does, how to install

Connects Claude Code to a local MCP server for persistent shells, process management, document analysis, and Obsidian vault maintenance.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin install desktop-commander@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-community
/plugin install desktop-commander@claude-community
/plugin marketplace add anthropics/claude-plugins-official
Open on GitHub

What desktop-commander does

The plugin bundles a local MCP server launched via npx -y @wonderwhy-er/desktop-commander@latest alongside specialized skills for workstation management. Claude Code gains persistent terminal shells, Windows PowerShell support, remote SSH sessions, port inspection, and process monitoring.

Additional skills handle read-only system health checks across CPU, memory, and disk, as well as configuration for claude_desktop_config.json and mcp.json. The package processes structured documents like PDF, DOCX, Excel, and large CSV files directly. Vector databases are not required.

Running the underlying server requires a working Node.js environment with npx.

What it helps with

  • maintain persistent terminal shells and SSH connections
  • inspect system health across CPU, RAM, and disk storage
  • configure MCP servers in claude_desktop_config.json and mcp.json
  • extract data from PDF, DOCX, Excel, and large CSV files
  • organize Obsidian notes with MOCs, properties, and wikilinks

Example prompts for the agent

  • Run a computer health check on CPU and disk usage
  • Establish an SSH session to inspect active listening ports
  • Organize orphan notes and update MOCs in my Obsidian vault

How to install desktop-commander

Plugin marketplace

/plugin install desktop-commander@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-community
/plugin install desktop-commander@claude-community
/plugin marketplace add anthropics/claude-plugins-official

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about desktop-commander

How to install desktop-commander in Claude Code?

First add the catalog by running /plugin marketplace add anthropics/claude-plugins-official, then run /plugin install desktop-commander@claude-plugins-official.

What does desktop-commander do?

It gives Claude Code access to a local MCP server for terminal management, SSH, system diagnostics, document parsing, and AI tool configurations.

What skills are included with the plugin?

It provides terminal, computer-health-check, ai-tools-setup, knowledge-base, obsidian-vault, and desktop-commander-overview.

Source text

claude · MIT
# Desktop Commander Claude Code Plugin

Desktop Commander gives Claude Code access to a local MCP server for terminal sessions, filesystem work, structured documents, search, process management, and SSH workflows — plus a set of skills that steer the agent toward those capabilities for common tasks.

## Components

- MCP server: `desktop-commander`, installed with `npx -y @wonderwhy-er/desktop-commander@latest`.
- Skill: `desktop-commander-overview` — explains when to use Desktop Commander MCP tools and how common workflows compose.
- Skill: `terminal` — persistent shells/REPLs, SSH, Windows PowerShell, process/port inspection, and saving recurring workflows as scripts.
- Skill: `computer-health-check` — read-only system health check (CPU, memory, disk, battery, startup) with safe, opt-in cleanups.
- Skill: `ai-tools-setup` — install, configure, and repair Claude Desktop, MCP servers, and local AI tooling (mcp.json / claude_desktop_config.json).
- Skill: `knowledge-base` — build and maintain a Markdown knowledge base any AI agent can navigate without a vector database.
- Skill: `obsidian-vault` — organize Obsidian vaults: MOCs, wikilinks, properties, Dataview/Bases dashboards, and orphan/link cleanup.

## Usage

Install the plugin in Claude Code, then ask Claude to use Desktop Commander when it needs persistent shells, long-running processes, local file reads, Excel/DOCX/PDF handling, large CSV analysis, remote SSH sessions, a system health check, AI-tooling setup, or knowledge-base/Obsidian organization.

For full project documentation, see the repository README.

© Desktop Commander · MIT · wonderwhy-er/DesktopCommanderMCP

Similar plugins

All plugins for Agent setup: memory, context, orchestration →

From the same set2

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor