Desktop Commander MCP for VS Code: Setup & Config

What you can do with Desktop Commander in VS Code

Give assistants a unified local workspace for files, documents, interactive terminals, and processes.

• Search directories and apply focused edits to documents or code.
• Run long-lived development commands and inspect output incrementally.
• Read and create PDFs or work with Excel and Word documents.

Before you start: Desktop Commander in VS Code

• Node.js for the npm configuration
• An MCP-compatible client

This is the README's manual MCP configuration. The setup command npx @wonderwhy-er/desktop-commander@latest setup can configure Claude Desktop instead. Restart the client afterward. Docker is documented as an alternative without local Node.js.

Desktop Commander VS Code configuration

1. Choose VS Code configuration scope

   For Desktop Commander MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Desktop Commander MCP to VS Code

   Use the DesktopCommanderMCP entry below in servers. Keep Desktop Commander MCP's documented stdio connection fields and your other VS Code entries.

3. Check Desktop Commander MCP in VS Code

   Desktop Commander MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "DesktopCommanderMCP": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@wonderwhy-er/desktop-commander@latest"
      ],
      "env": {}
    }
  }
}

Desktop Commander tools available to VS Code

Desktop Commander's stored tool list documents 26 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

get_config

Look for get_config among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Inspect the server's current configuration.

set_config_value

Look for set_config_value among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Change a configuration key; the tool warns to do this separately from file and execution chats.

read_file

Look for read_file among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Read local files or URLs, including PDF text and image extraction.

read_multiple_files

Look for read_multiple_files among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Read several files and associate each result with its path.

write_file

Look for write_file among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Write or append file content; dedicated tools handle PDFs and DOCX edits.

write_pdf

Look for write_pdf among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Create a PDF or modify an existing PDF document.

create_directory

Look for create_directory among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Create nested directories within allowed paths.

list_directory

Look for list_directory among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

move_file

Look for move_file among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

start_search

Look for start_search among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

get_more_search_results

Look for get_more_search_results among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

stop_search

Look for stop_search among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

list_searches

Look for list_searches among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

get_file_info

Look for get_file_info among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Read metadata such as file size, timestamps, permissions, and text line count.

edit_block

Look for edit_block among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Apply focused replacements to selected file content.

start_process

Look for start_process among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Launch a terminal process with state detection for command and data workflows.

read_process_output

Look for read_process_output among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Read a running process's output with offset and length controls.

interact_with_process

Look for interact_with_process among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Send input to a live process and collect its response.

force_terminate

Look for force_terminate among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Force an active terminal session to stop.

list_sessions

Look for list_sessions among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

list_processes

Look for list_processes among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

kill_process

Look for kill_process among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

get_usage_stats

Look for get_usage_stats among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

get_recent_tool_calls

Look for get_recent_tool_calls among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

give_feedback_to_desktop_commander

Look for give_feedback_to_desktop_commander among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

get_prompts

Look for get_prompts among VS Code's agent-mode tools after starting Desktop Commander through the MCP controls.

Desktop Commander: full stored tool descriptions

Troubleshooting Desktop Commander in VS Code

• Make npx @wonderwhy-er/desktop-commander@latest (Node.js/npm) available in the workspace, container, or remote environment hosting Desktop Commander MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
• Desktop Commander MCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: The npm installation route requires Node.js.
• Known limitation: Docker needs explicit folder mounts to access host files.
• Known limitation: Configuration changes carry a documented warning to separate them from execution and file-work chats.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions