MCP Connector

Control your desktop and execute commands from AI agents

Gives AI agents full local machine access: terminal execution, file read/write, process management, and in-memory code execution.

Works with claudecursorvscodechatgptpython
Updated 4 months ago
Version 1.0.0
Models

Add to Favorites

Why it matters

Enable AI agents to fully control your local machine by executing terminal commands, managing files and processes, and running code directly in memory without manual intervention.

Outcomes

What it gets done

01

Execute terminal commands and interact with long-running processes or SSH sessions

02

Read, write, and surgically edit text, Excel, PDF, and DOCX files on your filesystem

03

List, kill, and manage running processes on your local machine

04

Run Python, Node.js, and R code in memory without saving files to disk

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/desktop-commander-mcp | bash

Capabilities

Tools your agent gets

execute_command

Execute terminal commands and interact with long-running processes and SSH sessions.

read_file

Read text, Excel, PDF, and DOCX files from the filesystem.

write_file

Write and surgically edit text, Excel, PDF, and DOCX files.

list_processes

List all running processes on the local machine.

kill_process

Terminate a running process by ID or name.

interact_process

Interact with and manage running processes.

execute_python

Execute Python code in memory without saving files.

execute_nodejs

Execute Node.js code in memory without saving files.

+4 tools

Overview

Desktop Commander MCP

Gives AI agents full local machine access - terminal execution, multi-format file read/write with surgical editing, process management, and in-memory code execution - across any MCP-compatible client. Use when an agent needs genuine local-machine capability beyond a sandboxed interpreter; install with the same care as granting shell-level access, since it is not sandboxed.

What it does

Desktop Commander MCP gives an AI agent full access to a local machine: executing terminal commands and interacting with long-running processes or SSH sessions, reading and writing files across formats (plain text, Excel, PDF, DOCX) with surgical/targeted editing rather than full-file rewrites, listing/killing/interacting with running processes, and running code (Python, Node.js, R) directly in memory without needing to save it to disk first. It also handles instant ad-hoc data analysis of CSV, JSON, and Excel files on demand, and supports Remote MCP so it can be controlled from ChatGPT or Claude's web interface rather than only a local desktop client.

It works with Claude Desktop, Cursor, VS Code, Windsurf, and any other MCP-compatible client, making it a general-purpose local-machine bridge rather than a tool tied to one specific AI product.

When to use - and when NOT to

Use this connector when an AI agent needs genuine local-machine capability beyond a sandboxed code interpreter - running real terminal commands, managing actual OS processes, editing files across multiple formats with precise in-place changes, or executing code in memory for quick iteration without file management overhead. It's particularly suited to development workflows, data analysis tasks, and system administration where the agent needs direct machine access rather than a restricted execution environment.

Because it grants full terminal, filesystem, and process access, it should be installed and used with the same care as giving any tool shell-level access to a machine - it is not a sandboxed or restricted execution environment, and its capabilities (killing processes, writing arbitrary files, running arbitrary code) carry the same risk profile as direct terminal access for whoever's machine it's connected to.

Inputs and outputs

Input is a natural-language request routed through an MCP-compatible AI client - a command to run, a file to read/edit, a process to inspect or kill, or code to execute in memory. Output is the command's terminal output, the file's read/edited content, process status, execution results from in-memory code, or an ad-hoc data analysis result.

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

Capabilities

  • Terminal command execution, including long-running processes and SSH sessions
  • Full filesystem read/write across text, Excel, PDF, and DOCX formats with surgical editing
  • Process management: list, kill, and interact with running processes
  • In-memory code execution (Python, Node.js, R) without saving files
  • Instant analysis of CSV, JSON, and Excel data on demand
  • Remote control via Remote MCP from ChatGPT and Claude web

How to install

Run npx @wonderwhy-er/desktop-commander@latest setup for Claude Desktop setup. It's also available via GitHub (wonderwhy-er/DesktopCommanderMCP), the npm package @wonderwhy-er/desktop-commander, and configurable in any other MCP-compatible client (Cursor, VS Code, Windsurf), with a Discord community for support.

Who it's for

Developers and power users who want their AI agent to have genuine local-machine capability - running commands, managing files and processes, executing code in memory - across whichever MCP-compatible client they use, rather than being limited to a sandboxed execution environment.

Source README

Desktop Commander MCP gives AI agents full access to your local machine - execute terminal commands, read/write files, manage processes, and run code in memory. Works with Claude Desktop, Cursor, VS Code, Windsurf, and any MCP-compatible client.

Features

  • Terminal execution - run commands, interact with long-running processes, SSH sessions
  • Full filesystem access - read/write text, Excel, PDF, DOCX files with surgical editing
  • Process management - list, kill, and interact with running processes
  • Code execution in memory - run Python, Node.js, R without saving files
  • Instant data analysis - CSV, JSON, Excel files analyzed on demand
  • Remote AI control - use from ChatGPT and Claude web via Remote MCP

Install (Claude Desktop)

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

Links

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.