Data as of
Desktop Commander MCP for Cursor: Setup & Config
Desktop Commander MCP gives Cursor local file, document, terminal, and process-management tools.
What you can do with Desktop Commander in Cursor
Give assistants a unified local workspace for files, documents, interactive terminals, and processes.
- Analyze local CSV, JSON, or spreadsheet files through interactive processes.
- Read and create PDFs or work with Excel and Word documents.
- Manage active terminal sessions and operating-system processes.
Before you start: Desktop Commander in Cursor
- 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 Cursor configuration
Choose Cursor configuration scope
For Desktop Commander MCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.
Add Desktop Commander MCP to Cursor
Use the DesktopCommanderMCP entry below in mcpServers. Keep Desktop Commander MCP's documented stdio connection fields and your other Cursor entries.
Check Desktop Commander MCP in Cursor
Desktop Commander MCP: Enable in Cursor’s MCP settings; inspect tools.
Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
{
"mcpServers": {
"DesktopCommanderMCP": {
"command": "npx",
"args": [
"-y",
"@wonderwhy-er/desktop-commander@latest"
],
"env": {}
}
}
}Desktop Commander tools available to Cursor
Desktop Commander's stored tool list documents 26 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.
- get_config
Find get_config under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- set_config_value
Find set_config_value under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- read_file
Find read_file under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- read_multiple_files
Find read_multiple_files under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- write_file
Find write_file under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- write_pdf
Find write_pdf under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- create_directory
Find create_directory under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- list_directory
Find list_directory under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- move_file
Find move_file under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- start_search
Find start_search under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- get_more_search_results
Find get_more_search_results under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- stop_search
Find stop_search under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- list_searches
Find list_searches under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
- get_file_info
Find get_file_info under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Read metadata such as file size, timestamps, permissions, and text line count.
- edit_block
Find edit_block under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Apply focused replacements to selected file content.
- start_process
Find start_process under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Launch a terminal process with state detection for command and data workflows.
- read_process_output
Find read_process_output under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Read a running process's output with offset and length controls.
- interact_with_process
Find interact_with_process under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Send input to a live process and collect its response.
- force_terminate
Find force_terminate under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Force an active terminal session to stop.
- list_sessions
Find list_sessions under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Inspect active terminal sessions and their process state.
- list_processes
Find list_processes under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
List operating-system processes with CPU and memory information.
- kill_process
Find kill_process under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Forcefully terminate a process identified by PID.
- get_usage_stats
Find get_usage_stats under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Read tool usage, success rates, and performance summaries.
- get_recent_tool_calls
Find get_recent_tool_calls under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Inspect recent session tool calls with arguments and outputs.
- give_feedback_to_desktop_commander
Find give_feedback_to_desktop_commander under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Open the project's feedback form in a browser for manual completion.
- get_prompts
Find get_prompts under Desktop Commander in Cursor's MCP settings; inspect its arguments when the agent requests a call.
Retrieve a specific onboarding prompt by identifier.
Troubleshooting Desktop Commander in Cursor
- Cursor must find npx @wonderwhy-er/desktop-commander@latest (Node.js/npm) for Desktop Commander MCP. Enable the project/user entry in MCP settings and inspect its tools.
- Desktop Commander MCP uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.
Desktop Commander MCP — details. Cursor guide