Remote Desktop Commander

app.desktopcommanderPublished by desktopcommander.appOfficial publisherv1.1.25Updated Nov 11, 2026

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureFiles & StorageDeveloper Tools

Overview

AI-generated overview

Hosted MCP server that relays a secure connection to your own computer, letting an AI assistant read files, edit documents and run terminal commands remotely.

What you can do
  • Read and explore files: read files, read several at once, list directories, get file info
  • Search the filesystem: start, continue, stop and list active searches
  • Write and edit: write files, edit blocks, move or rename, create directories, write or modify PDFs
  • Run terminal and processes: start processes, send input, read output, list sessions and system processes, terminate sessions or kill processes
  • Manage devices and account: list paired devices, current user info, ping or shut down the device agent
  • Configuration and help: get or set configuration, prompt library, recent tool activity, usage statistics, submit feedback
When to use it
Useful when you want an AI app on the web, mobile or another machine to work on a computer you are not sitting at: building features, exploring codebases, editing Word, Excel or PDF files in place, or managing processes across several paired machines.
Requirements
A remote endpoint reached over Streamable HTTP with OAuth 2.0 sign-in. On each computer to control: Node.js 18 or newer for npx, and a terminal running the device agent, which pairs through a browser verification code. macOS, Windows and Linux are supported; the agent must stay running for access.
Before you install
Tools run with your user account's permissions on the paired machine, so a connected AI account is effectively a credential — protect it with MFA. The agent can write, move and delete files and start or kill processes. The hosted service is proprietary and relays data through a third party; revoke devices from the dashboard and stop the agent to end access.

Installation

In SourceWeft

  1. Open Remote Desktop Commander in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.desktopcommander%2Fremote-desktop-commander/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "remote-desktop-commander": {
      "type": "http",
      "url": "https://mcp.desktopcommander.app/mcp"
    }
  }
}

README

Remote Desktop Commander

[Remote Desktop Commander]

Build, explore, automate on your computer — from anywhere.

Reach your computer's filesystem and terminal from any AI app that supports remote MCP connectors. Remote Desktop Commander is a hosted MCP server that relays a secure connection to your real machine, giving your AI assistant the same full file and shell access as the local server — without you needing to be at the keyboard.

[Add to Cursor]

This repository hosts the public manifests, documentation and issue tracker for the hosted service. The service implementation is not open source. For the open-source local (stdio) server, see DesktopCommanderMCP.

What you can do

  • Build from scratch — create features and applications with simple commands
  • Manage development environments — set up servers, configure systems, handle processes
  • Explore existing codebases — navigate and understand complex repositories
  • Edit documents in place — work on Word, Excel, and PDF files where they live on disk
  • Manage context and documentation — keep track of project details and technical specifications
  • Control multiple machines — pair several computers and address them by name in one conversation

Quick start

1. Start the device agent

On the computer you want to control:

bash
npx @wonderwhy-er/desktop-commander@latest remote

Your browser opens to a verification page showing a pairing code (also printed in the terminal — a standard OAuth device-flow check). Sign in, confirm the codes match, and the terminal reports "Device ready". Keep the agent running: close the terminal, no access.

2. Connect your AI client

Each client walks you through OAuth sign-in on first connect.

claude.ai / Claude Desktop — Settings → Connectors → Add custom connector, then enter:

https://mcp.desktopcommander.app/mcp

Claude Code:

bash
claude mcp add --transport http remote-desktop-commander https://mcp.desktopcommander.app/mcp

(If you work inside a checkout of this repo, Claude Code also picks up the included .mcp.json automatically.)

ChatGPT — Settings → Apps & Connectors → Advanced settings → enable Developer mode (requires a plan that includes it), then Create connector and enter:

https://mcp.desktopcommander.app/mcp

Cursor — one click: Add to Cursor. Or add to ~/.cursor/mcp.json manually:

json
{  "mcpServers": {    "remote-desktop-commander": {      "url": "https://mcp.desktopcommander.app/mcp"    }  }}

VS Code — install the agent plugin (bundles this server):

bash
copilot plugin install desktop-commander/remote-desktop-commander

Or add the server directly to .vscode/mcp.json in your workspace (or your user-level mcp.json):

json
{  "servers": {    "remote-desktop-commander": {      "type": "http",      "url": "https://mcp.desktopcommander.app/mcp"    }  }}

Gemini CLI:

bash
gemini extensions install https://github.com/desktop-commander/remote-desktop-commander

3. Try it

These work against any machine running the agent, no setup needed:

"List the contents of my home directory and tell me what's there."

"Create a folder called ai-test in my Documents folder. Inside it, write a short Python script that prints the date, and run it."

"Start a Python REPL on my machine, import pandas, and tell me which version is installed. Keep the session alive."

"Search my home directory for files modified in the last 24 hours and group them by folder."

Full walkthrough with troubleshooting: docs/SETUP.md

Requirements

  • Node.js 18 or newer (for npx) on each computer you want to control
  • One terminal running the device agent per machine
  • Works on macOS, Windows, and Linux

Available tools

CategoryTools
Read & exploreRead File, Read Multiple Files, List Directory, Get File Info
SearchStart Search, Get More Search Results, Stop Search, List Active Searches
Write & editWrite File, Edit File Block, Move or Rename File, Create Directory, Write or Modify PDF
Terminal & processesStart Process, Send Input to Process, Read Process Output, List Active Sessions, List System Processes, Terminate Session, Kill System Process
Devices & accountList Paired Devices, Current User Info, Ping Device, Shutdown Device Agent
Configuration & helpGet Configuration, Set Configuration Value, Get Prompt Library, Get Recent Tool Activity, Get Usage Statistics, Submit Feedback

How it works

mermaid
sequenceDiagram    participant AI as AI app (web, mobile, desktop)    participant S as mcp.desktopcommander.app    participant D as Your computer (device agent)    AI->>S: MCP tool call (OAuth 2.0 bearer)    S->>D: relayed to your paired device    D->>D: executes locally    D->>S: result    S->>AI: MCP response
  • Authentication is standard OAuth 2.0 with PKCE; devices pair via the OAuth device authorization flow (the short-code approval you see at setup).
  • The server only accesses data explicitly requested through tool calls; transmission is encrypted in transit (HTTPS/TLS).
  • A machine is reachable only while its device agent is running — stop it with Ctrl+C and access ends. Devices can also be reviewed and revoked at any time from the dashboard.
  • Tools execute with your user account's permissions on the paired machine, so treat your connected AI accounts like credentials and protect them with MFA. Read the full trust model in SECURITY.md.

Support & legal

Related

Source: README.md at commit b480501

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

6
  1. v1.1.21Nov 5, 2026
  2. v1.1.16Oct 29, 2026
  3. v1.0.80Oct 22, 2026
  4. v1.0.79Oct 20, 2026
  5. v1.0.75Oct 13, 2026
  6. v1.0.3Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.